Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When we have cy-grep implemented to select specific tests, running it via cypress-parallel leads to failure while building report (causing buildkite build to fail) #174

Open
prabodhkelkar opened this issue Oct 5, 2023 · 0 comments

Comments

@prabodhkelkar
Copy link

When we have cy-grep implemented to select specific scripts for executions, running it via cypress-parallel leads to failure while building report (causing buildkite build to fail)

I have implemented tags to select specific test scripts for executions using cy-grep (https://github.com/bahmutov/cy-grep). The execution script used is as below -
"cy:nxs-dev-original": "npx cypress run --env fileConfig=nxs-dev,grepTags=@NXS-DEV --browser chrome"

With cypress-parallel, the execution script becomes -
"cy:nxs-dev-parallel": "cypress-parallel -s cy:nxs-dev-original -t 2 -d 'cypress/e2e/05*/*.cy.ts' -r 'cypress-mochawesome-reporter' -o 'cypressParallel=true'"

Cypress specs directory specified above has 2 spec files, but only one has "@NXS-DEV" tag. So, only will get executed to generate report file. But, when execution is complete, cypress-parallel compares "Test suites found" (which is 2 in this case) with "Test suite results" (which is 1). As this does not match, Error is returned to buildkite - causing the build to fail.

image

Can we add an option to not compare this "Test suites found" with "Test suite results"?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant