No, I haven't

One way to use tags is with the cypress-grep plugin:https://github.com/cypress-io/cypress-grep Another option is switch between multiple configs: - versions < v10: https://docs.cypress.io/api/plugins/configuration-api#Switch-between-multiple-configuration-files - versions v10+: I do not have a first-class example, but you will need to update your config since

cypress/plugins/index.js

is no longer supported

On the Cypress Dashboard it would be nice to be able to hide unwanted tags from the list. The first few times I used tags I had syntax errors on my command line, so I have a few unwanted tags in the list with extra characters and there's no way to get rid of them. A bit annoying.

I believe if you delete the runs that correspond to that tag, they'll stop appearing in the list. I'd try that, at least.

@Thak you very. I will look into that. Appreciate your help a ton.

That was the first thing I tried; no worky, sadly.

I've asked for this feature for a while now. Hopefully it'll be added one of these days

Hey! I wanted to ask what would be the best practice for separating different pipeline runs (or, environments runs) in the dashboard. I have the same code base for all environments using env variables. Would the best way to achieve that will be by grouping?

Using tags will be helpful in the dashboard. Just be sure to think ahead for what you want the tags to be. You can't currently delete tags from the dashboard UI (as @late-planet-4481 just pointed out)

Hmm, seems from what I can see that it's not exactly that use case. Looks like tags are used by adding the tag for each describe/it block. What I need to do is to split separate runs from separate pipelines, as I have one modular codebase for all environments.

Tags are specified on the command line, not the

it()

block, so they should be suitable for your use case https://docs.cypress.io/guides/guides/command-line#Commands

Ah, my bad. I was looking at a documentation of a tag plugin. Thank you, much appreciated.

You're welcome 🙂

@incalculable-crowd-80129 did you figure this out? if not, you could try enabling debug logging on the client to get some more info: https://docs.cypress.io/guides/references/troubleshooting#Print-DEBUG-logs

@late-planet-4481 @fresh-doctor-14925 currently there isn't a way to hide tags, but i posted this internally to add to our collection of community feedback

thank you!

I have a very simple e2e test that is essentially "Log in and see the protected page content". I have a Ruby on Rails backend, which houses the login page and a React frontend that we redirect to after sign in. I was able to get that all working locally using the

experimentalSessionAndOrigin

features. The problem I am facing is that, when running in a multi-container setup in CI on Gitlab, I am getting 401s on the API requests that the Frontend makes because the session cookie isn't being passed along in those requests. I have a working test suite with this setup in Cucumber so there shouldn't be anything fundamentally wrong. If I run both the Rails application and Frontend project on the same container in Gitlab, everything works as expected. CORS is setup properly for this setup and the cookies are set with SameSite=Lax in CI. Has anyone experienced this issue before that can shed some light?

Hi! I just found out that nowhere in the Cypress dashboard I can find information against which environment my tests ran. We use feature branches & review apps to test our stuff and all the Cypress tests run against different testing domains. But when a test fails, I can't find in the Cypress dashboard which URL it tested against. Am I overlooking something or is it simply not there? It also doesn't say in the test output itself. Edit; I could see it in the video, but I've disabled videos.

Hi @shy-van-7331 There are a couple of options that can help you to locate your testing environments: * You can check your Test Definition in the panel on the right side of the Dashboard * You can use separate Projects to determine which environment is used: https://docs.cypress.io/guides/dashboard/projects * You can add

--tag

as an option to your

cypress run

command: https://docs.cypress.io/guides/guides/command-line#Options

Unfortunately the test definition doesn't show the URL

Yeah I know about the

---tag

parameter. I've for now solved it by just echoing the URL out in our CI/CD job. But still seems weird to me I can't find it in the dashboard by default.

Understood. We are always looking to improve the experience with the Dashboard. I am happy to share your feedback with the Product team after a GitHub issue is created: https://github.com/cypress-io/cypress/issues/new?assignees=&labels=&template=3-feature.yml

Done https://github.com/cypress-io/cypress/issues/23549

Excellent! I have shared your feedback with our Product teams!

Hi, another question. Why are badges only available for public projects? https://www.cypress.io/blog/2020/09/02/highlight-your-projects-test-status-with-cypress-readme-badges/ We use Gitlab for our internal projects and I like to add a badge there to see whether the Cypress tests failed or not.. I now have to build something myself 😦

Highlight your project’s test status wit...

This is due to a third-party restriction, but I will definitely bring it up internally. You're not the firs to ask for this.

Hi, Is there any way to set a test as: Test which we know fails but does not want it to break the build. (for example if we already opened an issue on that bug and want to ignore it from now)

Was looking for a different way, So the test will run but will not fail the pipeline.