I agree with this thread, the limit should be configurable.
The company I worked for have 60+ different websites, and I am in charge of checking their login health after updating the login portal.
I have large preparation time, but only < 30 mins for actual testing .
Without the limit I can do the following:
- Open the 60 browser on 0:30 a.m., tell all my 60 parallel login checking script to wait till 1:00 a.m.
- Stop using my computer for 30 mins, so all of the browser are ready to go
- Deploy the update on login portal on 0.55 a.m.
- on 1.00 a.m. all script executes, and check if the login is success, takes less than 1 mins to do.
With the above method, without the limit I can take < 10 mins for the whole test.
If the limit is applied, I am going to takes 30 mins to test which is a big nono.
It is so critical for my workflow that I cannot upgrade to version above 5.7, hopefully the team can understand the importance of a configurable limit. Thanks.