Support running tests in parallel
See original GitHub issueWe are using Radish to describe features executed by Selenium, and being able to run in parallel is essential for delivering results in a timely fashion.
I suspect a --processes argument to radish would probably be the correct interface for this.
I will investigate implementing this on my own, but if there’s any other work out there to support this, I would love to hear about it.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:11 (4 by maintainers)
Top Results From Across the Web
Running Tests in Parallel > xUnit.net
Running unit tests in parallel is a new feature in xUnit.net version 2. ... we mean specifically is how a test framework may...
Read more >Running Tests in Parallel | TestComplete Documentation
Supported test types Only the following tests can run in parallel: Cross-platform web tests. These tests can include operations that simulate user actions...
Read more >Run VSTest tests in parallel - Azure Pipelines | Microsoft Learn
Running tests in parallel is a great way to improve the efficiency of CI/CD pipelines. This can be done easily by employing the...
Read more >A complete guide to parallel testing - HeadSpin
The blog walks us through the basics of parallel testing, its benefits, implementation, challenges, and the best-in-class parallel testing ...
Read more >Parallel Testing: The Essential Guide - BrowserStack
Parallel Testing is a process to leverage automation testing capabilities by allowing the execution of the same tests simultaneously in multiple ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

OK, I’ll begin looking into refactoring the generic functionality out of the wrapper into something we can share. No promises, but hopefully we can share something useful.
Threads for each scenario( including a thread for each scenario in Scenario Outlines! ) is also what https://github.com/grosser/parallel_tests is doing.
Since the idea behind having parallel tests is that you want to minimize the run time as much as possible, I think the complications are worth it. A switch between “run a thread per scenario” and “run a thread per feature” would be ideal( see
--group-byin parallel_tests).