feature request --run_per_test=100

[leblancmeneses]

Hi Brandon,

Would it be possible to add a simple e2e test that just verifies the title of the page with buildbuddy on this project?

The biggest win for my organization would be to execute our e2e tests with --run_per_test=100 to deflake the e2e tests.

rules_nodejs project has this cypress sample:
git clone https://github.com/bazelbuild/rules_nodejs.git
cd rules_nodejs/examples/cypress
bazel test :test --runs_per_test=4 --config=remote --disk_cache=

The problem I have on buildbuddy is I need to supply my own docker image
--experimental_docker_image=
https://github.com/cypress-io/cypress-docker-images

the cypress sample yields

Read our documentation on dependencies for more information:
https://on.cypress.io/required-dependencies
If you are using Docker, we provide containers with all required dependencies installed.
----------
Error: spawn Xvfb ENOENT

because it is using the default gcr.io/cloud-marketplace/google/rbe-ubuntu16-04

thanks

[bduffany]

Hi Leblanc, Cypress rules currently don't play very well with remote execution, and we're looking into it. Another avenue might be to check out https://github.com/bazelbuild/rules_webtesting -- I'll try and see if I can get an example working.

[leblancmeneses]

There is also https://github.com/bazelbuild/rules_nodejs/blob/8bbc27bbdf3999fc5fb9d751279e102dbf3a9149/docs/Protractor.md
I can try adding a test using that rule for protractor. The biggest piece for remote execution is isolated container for port given e2e will launch 'ibazel run //server:main_dev' 'ibazel run //app:devserver --config=vanilla' and I want a lot of instances for deflaking.