Please provide pointers to setup Selenium Hub or equivalent for Taiko/Gauge with JS

[james-k-mathew]

We are using Taiko + Gauge with JS
We need to run many scripts in parallel across multiple machines
Is there a way to setup Selenium grid for the (Taiko + Gauge with JS) or
is there any other equivalent way to do it

[harimadusumilli]

Yes, any pointers and documentation will be helpful. I am also looking for this documentation and ways to set it up.

[NivedhaSenthil]

selenoid can be used for this usecase I feel...there is plugin for the same

@saikrishna321 might have more context on this

[saikrishna321]

@harimadusumilli @james-k-mathew I use Selenoid as grid and trigger the test in parallel. Each test will spin a new cluster in parallel.

[james-k-mathew]

@NivedhaSenthil @saikrishna321 , thank you very much, will look into it

[saikrishna321]

Hi! I haven't tried ggr before. Looking at the error looks like your selenoid.config.js is missing the port and host.

[james-k-mathew]

hi @saikrishna321 I changed to this configuration. AWS Linux instance with SelenoidTaiko plugin -> AWS Linux instance with Ggr -> AWS Linux instance with slave Selenoid

Now from the AWS instance with SelenoidTaiko plugin, I am able to create instance in slave Selenoid by using the openBrowser command of Taiko. It was also possible to hit the slave Selenoid directly by using its url and port.

Earlier I was having the SelenoidTaiko plugin in a Windows machine and using openBrowser was leading to errors.

[saikrishna321]

@james-k-mathew Great you got it working. Can you please add this info to the taiko-selenoid ReadMe?

[james-k-mathew]

@saikrishna321 I was using a slightly different configuration. Selenoid, taiko-selenoid plugin, Gauge and Taiko in the same LInux instance. I tried to run many tests in parallel mode this time. After some time the tests were failing with afterSuite failure and screen shot taking completely failing.
After I tried to see where the problem could be, I realized that the test was timing out at 3 minutes, whether all the tests in all the threads were completed or not.
Saw that the sessionTimeout variable in the node_modules/taiko-selenoid/lib/index.js file was set to 3m. After I changing it to 30m the tests started running properly without getting timed out/afterSuite failing/not taking screenshot.

[saikrishna321]

@james-k-mathew The latest master on taiko-selenoid has this fix to configure the session timeout using setSelenoidConfig

saikrishna321/taiko-selenoid@daf0066#diff-d40fbd8da63e458ea729a9b8e0ac654aa6bd68e07f014acfc93a6506f1ffe863