You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 24, 2018. It is now read-only.
Hi , I am responsible with E2E jasmine environment testing which currently runs on cloud test suppliers (browserStack & sauceLabs) , on top of a protractor&selenium.
i stumble over your solution by chance and wanted to learn more about you guys as the current cloud testing mechanism is sometimes flaky and not stable.
you are describing the headless mode as a method for the AWS LAMBDA
can i run jasmine tests in parallel mode locally on dockers ? or this is exclusive to AWS ?
thanks in advance !
The text was updated successfully, but these errors were encountered:
so basically are you saying i am able to run only 1 instance per docker of chrome ?
it means that if i have 400 e2e tests , and i want to run them all parallel i need 400 dockers. i know https://github.com/OnetapInc/chromy can run multiple instances on the same machine.
Hi @JOEAV — We don't yet have a Docker solution. Chromy has support for controlling multiple tabs at once, however by running concurrent tests in multiple tabs you end up sharing resources between the multiple tabs, defeating the performance benefit of running tests concurrently. The Chromeless Proxy currently only supports AWS Lambda — there you can run 400 e2e tests in parallel.
Hi , I am responsible with E2E jasmine environment testing which currently runs on cloud test suppliers (browserStack & sauceLabs) , on top of a protractor&selenium.
i stumble over your solution by chance and wanted to learn more about you guys as the current cloud testing mechanism is sometimes flaky and not stable.
you are describing the headless mode as a method for the AWS LAMBDA
can i run jasmine tests in parallel mode locally on dockers ? or this is exclusive to AWS ?
thanks in advance !
The text was updated successfully, but these errors were encountered: