question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Issue running tagged tests with cypress-tags

See original GitHub issue

Description

I am testing the cypress-tags run -e TAGS='not @foo and (@bar or @zap)' feature in my project but I’ve found a problem when trying it out.

When I run cypress-tags run -e TAGS='@login' it works as expected, running only the scenarios tagged as login but when trying the opposite cypress-tags run -e TAGS='not @login' I get this errors:

$ cypress-tags run -e TAGS='not @login'
Error parsing tags: 'not'. Message: empty stack
Error parsing tags: 'not'. Message: empty stack
Error parsing tags: 'not'. Message: empty stack
Error parsing tags: 'not'. Message: empty stack
Error parsing tags: 'not'. Message: empty stack
Error parsing tags: 'not'. Message: empty stack
Error parsing tags: 'not'. Message: empty stack
Error parsing tags: 'not'. Message: empty stack
Error parsing tags: 'not'. Message: empty stack
Error parsing tags: 'not'. Message: empty stack

So what it does is it tries to run all the scenarios but since not one matches the criteria all of them are set to passed without running them.

My versions are:

"cypress-cucumber-preprocessor": "^1.16.2"
"cypress": "3.6.1"

Ubuntu 18.04.3 LTS

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:9 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
badeballcommented, Apr 20, 2021

@davidzambrana, your script yarn test:error would work if you quoted correctly, a

{
  "test:error": "./scripts/run-local-task.sh cypress-tags run -e TAGS=\\'not @skip\\'"
}

… alternatively, you can replace eval with exec and leave the quoting as is. You probably don’t want a subshell to begin with anyway.

1reaction
lgandeckicommented, Nov 28, 2019

would you be able to create a simple demonstration/reproduction? Maybe based on a fork of one of our example repos? That will increase the chance that one of us will find the time to investigate and fix 😃

Thanks!

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to apply Tags to your Cypress Tests like Smoke, E2E
Method 1: Using cypress-select-tests (This is DEPRECATED) · Method 2: Using a Custom Function · Method 3: Using cypress-grep · About The Author ......
Read more >
How To Tag And Run End-to-End Tests - Gleb Bahmutov
How to tag your Cypress tests to make sure anyone can quickly test the changes. · Organize the tests by feature # ·...
Read more >
cypress-tags - npm
Use custom tags to slice up Cypress test runs. See cypress-tags-example for a working example. This plugin uses TypeScript to parse the tests, ......
Read more >
Issue running tagged tests with cypress-tags #274 - GitHub
I am testing the cypress-tags run -e TAGS='not @foo and (@bar or @zap)' feature in my project but I've found a problem when...
Read more >
Cucumber tags are not working after Cypress ... - Stack Overflow
Just remove cypress-tags altogether, but a good enhancement is to add filterSpecs and ... One of it's features is the run tests by...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found