parallel_process_delay test setting not working with Nightwatchjs upgraded version 3.2.1

[aakanksha88]

Description of the bug/issue

We have been using the test setting 'parallel_process_delay' in our nightwatchjs automation framework with version 2.6.19 and it has been working fine.

When we upgraded the nightwatch js version to 3.2.1, we found that the test setting 'parallel_process_delay' is not working with parallel execution.
All the test suite execution starts at once without any delay irrespective of how many milliseconds we pass as a value for this test setting in nightwatch.json. We tried with 10000 and 20000 ms but none helped.

Could you please also provide some inputs on how we can achieve parallel process delay, it will be of great help. We need to access our application which has some restrictions on how many requests we can send once due to which we need to introduce some delay between the requests.

Our test automation framework has around 450 test suites and 5000+ test cases automated which we execute on Selenium Grid daily basis using parallel execution.
This is a blocker for us as due to the restriction mentioned above, we need to introduce some delay in the requests we are sending and currently we are not able to introduce any delay which is leading to test suite failures on large scale.

Thanks in advance.

Steps to reproduce

Add test setting in nightwatch.json
"parallel_process_delay" : 10000

Nightwatch Configuration

In nightwatch.json
"parallel_process_delay" : 10000

Nightwatch.js Version

3.2.1

Node Version

16

[aakanksha88]

Hi @gravityvi As mentioned in reported issue we need this test setting for our test suite execution, could see this issue is categorized as bug, could you please help us know by when this will be fixed ?
Thanks in advance

[marian-r]

Ran into the same issue. @gravityvi have you had a chance to look into this?

[marian-r]

@aakanksha88 I found a workaround by setting use_child_process: true which forces a different implementation of parallelism. Hope this helps while this gets fixed for the worker threads implementation.

[cnavy2]

@marian-r In the above workaround by setting use_child_process: true parallel execution looks similar to what we have in Nightwtach 2.6.19 . So, I am not sure if we can proceed with Nightwatch Upgrade to 3 with this settings.

@gravityvi Could you please help us by letting us know by when this will be fixed?

Thanks in Advance.

[gravityvi]

@cnavy2 @aakanksha88 I will try to allot some time to this. I have been a little busy with my day job. Most probably I will take this up over the weekend 😄

[cnavy2]

Hi @gravityvi, Could you please prioritize this bug and provide fix for this. It was a blocker for us to upgrade to Nightwtach.js 3.
Thanks In Advance.

[gravityvi]

Hey @cnavy2 @marian-r @aakanksha88 👋🏻 , I have a raised a PR to fix this issue.

[marian-r]

Awesome, thank you very much 👍

[cnavy2]

Big Thanks!!