Skip to content
This repository has been archived by the owner on Nov 24, 2018. It is now read-only.

local support for headless mode #237

Closed
JOEAV opened this issue Aug 15, 2017 · 3 comments
Closed

local support for headless mode #237

JOEAV opened this issue Aug 15, 2017 · 3 comments
Labels

Comments

@JOEAV
Copy link

JOEAV commented Aug 15, 2017

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 !

@sul4bh
Copy link
Contributor

sul4bh commented Aug 15, 2017

You might find this thread helpful: #88 (comment)

@JOEAV
Copy link
Author

JOEAV commented Aug 15, 2017

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.

@adieuadieu
Copy link
Collaborator

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants