Add cypress_test e2e testing rule

[Toxicable]

🚀 feature request

Description

A more DX friendly e2e testing rule

Describe the solution you'd like

cypress_test rule with support for ibazel test/run - cypress open and bazel test/run - cypress run

Describe alternatives you've considered

protractor_web_test_suite

Current blocking issues

Test

• Cypress tries to touch the Read Only FS during bazel test - Cypress should not require write access of root folder cypress-io/cypress#1281

Run

• Cannot run cypress.run with no cypress.json - Running cypress with no project: false actually runs cypress open cypress-io/cypress#3675

ibazel

• Cannot specify what specs to run during cypress open - Support for --spec with "cypress open" cypress-io/cypress#1925

[Globegitter]

One way to get around the write issue from bazel's pov is by adding the --sandbox_writable_path=/ but that is of course not great as it renders that the read-only FS useless.

Also what is strange, we started to integrate cypress into our bazel CI setup recently (in a quite "quick and dirty" way) and while I do get the read-only FS error when running bazel test locally strangely enough our circleci setup just works:

It looks like this is your first time using Cypress: 3.2.0

[19:22:17]  Verifying Cypress can run /home/circleci/.cache/Cypress/3.2.0/Cypress [started]
[19:22:19]  Verified Cypress!       /home/circleci/.cache/Cypress/3.2.0/Cypress [title changed]
[19:22:19]  Verified Cypress!       /home/circleci/.cache/Cypress/3.2.0/Cypress [completed]

I am really not sure how that is possible, I can only guess it has something to do with the docker setup we are running there.

[Toxicable]

@Globegitter Is Cypress possibly working outside of the Bazel directories?

[Globegitter]

Yeah that could be, I am still not sure however what the real difference is between the circleci setup and my local one. But I guess I would just need to spend some time investigating. And while it is a bit worrying the positive aspect about it is we can use it now already in our CI setup.

[marcus-sa]

What's the progress on this?

[Toxicable]

We're still blocked on Cypress.
Check the related issues for any updates

[yohcop]

I think the 2 referenced issues on cypress were fixed! :)

[abhinaba-ghosh]

@Globegitter , Hi, do you have any documentation or example project to make cypress work with bezel? Any guidance will help!

[marcus-sa]

@abhinaba-ghosh there's a PR to add cypress rules to rules_nodejs #1930

[mattem]

#1930 is now merged and released as part of 2.0.0 so this issue can be closed I think.
Example here