badeball / cypress-cucumber-preprocessor

Run cucumber/gherkin-syntaxed specs with Cypress
MIT License
1.32k stars 147 forks source link

When running a mixed set of specs, test reports exclude the test results of non-cucumber specs #1171

Closed serhatgemici closed 6 months ago

serhatgemici commented 6 months ago

Current behavior

When I execute a set of mixed specs {cucumber, cy.js}, and check the reports, I see that there are only the results of the cucumber specs, and the cy.js spec test results are missing on html, json and messages reports.

Desired behavior

When a mixed suite is executed, it would be really great to have the test reports containining all tests results rather than excluding the results of the cy.js type of mocha specs.

Being able to mix the spec types is really great, but only getting the partial test report out of a test run is kind of taking away the usefulness of that great feature.

Test code to reproduce

To reproduce the issue on an isolated environment, all that's needed is to checkout to this repo and follow the steps below: https://github.com/serhatgemici/specResultsExcludedInTestReports

the repo contains a reduced test case based on esbuild-cjs example with mixed spec files {1 cucumber and 1 non-cucumber}

npm i

and then

npm run test:chrome

Check the test reports in

reports/html/ reports/json/

--> Test reports only contain cucumber specs.

Versions

Checklist

badeball commented 6 months ago

This is unfortunately intended behavior. There's no good way of representing a non-cucumber spec in a cucumber report. Closing as it's not a bug.