Be able to run cypress/included on an Nx workspace

What would you like?

I would like to maintain the less possible code in order to execute my Cypress tests on an Nx workspace 😁.

As I explained here, for the moment I maintain my own Docker image, with Cypress included for running the Cypress tests of my Nx workspace (this image is shared across developers and CI machines and the command used to run tests is the Nx one).

Few days ago, I discovered this article, presenting cypress/included and I would be very happy to use it as a single Cypress source of truth. Unfortunately I am not able to run it on an Nx workspace (I tested it on a classical Angular app and liked it a lot 😋).

Why is this ~needed~ wanted?

Nx workspaces are very powerful and popular, providing a “ready-to-go” image to its users could improve their dev(ops) experience (in fact, I know several companies which would be very interested in this strategy for running their Cypress tests).

Note

Following the discussion in the abovementioned issue, I am considering the fact this feature could be transformed in a “documentation feature” because I suppose the issue can be solved by mounting the correct files in their correct places. Does anyone have an idea of something which could match in this case?

[weyert]

Personally, I would advise to make a reproducible repository. I would happy to have a look but don’t have the time to recreate your setup

[hadrien-toma]

I am now able to use the cypress/included image only as I wanted. What I have done:

• Use --entrypoint docker run argument in order to set it to /bin/bash and bypass the default cypress command execution
• Mount the Nx workspace in the container
• Set the Docker container “working directory” to the Nx workspace
• Execute the standard npm run nx e2e command inside the container

Simple, efficient, with nearly 0 technical debt, thank you very much Cypress team to provide this included image! 😍