Propose cypress/run as a command

[lbesson-della]

Unless I'missing something there is no command equivalent to the run job.

In my case I would like to run a slack notification on whether the tests failed or not.

If I use the cypress/run job, the slack job cannot be run when the tests fail. If I want to create a job that runs the test and, as final step, runs the slack command, I have a lot of code to write to match the functionality of the cypress/run job.

Having a run command almost equivalent in terms of functionalitu to the run job, that would be great

[traviscrist]

We would like this as well. It seems cypress/run is just a job so it can't be made into a reusable command. This means we have to copy the code to run the cypress/run job into multiple workflows. Having it run as a command would make things much more reusable.

[kevnm67]

I'd also appreciate this. An equivalent run command would add value → flexibility and improve reuse. If not, thoughts on providing params to inject steps?

I appreciate y'all's consideration and providing this orb.

@lbesson-della for slack try using post-steps.

post-steps:
    - slack/notify:
          event: fail
          ...

[jennifer-shehane]

Please try v3.0.0 of our orb. We have a cypress-command command where you pass the command to run Cypress as you normally would in a termianl.

cypress-command: 'npx cypress run --record --parallel'

We believe this offers more flexibility which may resolve your issue. Please open a new issue if 3.0.0 does not resolve your issue.