Running npx cypress run is not creating the folder /test-results with the failed tests

[CaiqueCoelho]

I'm using Cypress in version "13.15.0" and when I run Cypress with npx cypress run --env grepTags=@TestFail I have some Cypress tests failing but the folder /test-results is not created.

I'm using the tag @TestFail to target some specific tests I know will fail

I have also run npx cypress-plugin-last-failed run --e2e --browser electron to see if the plugin installation was fine and I just got:

No previous failed tests detected
Ensure you are in the directory of your cypress config
Try running tests again with cypress run

Could you please help me? I can give you more details if you want

[dennisbergevin]

Hi @CaiqueCoelho thanks for reaching out!

An initial question:

Can you check to ensure you've followed the plugin's Installation instructions thoroughly?

The absence of a test-results directory being created may be pointing to missing the collectFailingTests within setupNodeEvents in the config.

[CaiqueCoelho]

Hey @dennisbergevin thank you so much for your quick answer and help.

I read all the installation instructions again and looks like everything is fine The file below is my setupNodeEvents exported into a separate file

The funny thing is, running in the open Cypress mode the plugin works perfectly, but I see even this way the folder is not created, but I'm not sure if the folder is only created in the run mode

Is there any debug mode I can add to see any logs? I'll try some experiments tomorrow, and if I discover anything new, I'll share the details here. Thank you so much

[dennisbergevin]

Hey @CaiqueCoelho, thanks for the reply.

The open mode will not create a test-results directory, as the toggle pertains to filtering failed tests per each spec file respectively.

Without really understanding your setupNodeEvents setup, my overall suggestion for debugging would be to remove or comment out everything in your setupNodeEvents other than the following pieces:

...
    setupNodeEvents(on, config) {
      collectFailingTests(on, config);

      require('@bahmutov/cy-grep/src/plugin')(config);
      return config;
    },
...

Ensure the plugin works as intended from this setup, then, work backward by adding a little more back into your setupNodeEvents and observe the behavior.

Please feel free to reach out with any more questions or concerns, or if you find a solution feel free to share here.