checkly
As a user I want an option to ensure a set of browser checks do not run in parallel
💡 For general support requests and bug reports, please go to checklyhq.com/support
Is your feature request related to a problem? Please describe. Since our application has a state, browser checks running in parallel can cause strange behaviour that makes the test results inaccurate
Describe the solution you'd like Easy option: A setting that ensures that no two browser checks in the whole set will every run at the same time.
More complex option: Allow grouping of browser checks with the same setting, allowing checks from different groups to be run in parallel, but not checks in the same group.
Describe alternatives you've considered We may have to create different projects on our test user to ensure that tests don't collide, but this will make our testing code much more complex, require much more setup, and also not test as many edge cases.
Additional context Our application is a drawing tool similar to Figma, and we want to run tests where we add, remove and manipulate different shapes.
@olavblj thanks for reporting this. I understand your request, but I see many issues with providing a stable solution. Similar to unit tests, a check run by Checkly should autonomous with no side effects on other checks. The reason is that the duration and effects of a check are never 100% predictable due to latency, the internet being unpredictable etc.
Any feature that would allow checks to depend on other check (or the inverse) will come with some thorny side issues that will impact the reliability and cause flakiness.
Your request is still valid, and sequencing checks is certainly something that we can look into.
