Parallel Testing World
summary
A patch called parallel_test patch runs Test::Unit test files concurrently so ruby's make test-all completes far faster; the implementation uses a master/worker with IO.popen model (workers accept filenames, run tests, stream results back, master redistributes work and quits workers when done). Practical fixes include isolating tests by unique ports, temp filenames and explicit requires. Real-world numbers: a suite drops from about 121.4s to 43.41s (roughly 2.8× faster), and the feature is merged and usable.
AI-written summary · about
chapters (8)
- 0:00Introduction and context
- 3:38Benefits of parallel testing
- 8:14Understanding the mechanisms
- 10:06Implementation details
- 16:30Addressing testing issues
- 21:00Performance results
- 23:44Usage and conclusion
- 28:39Q&A and closing
related talks
31mReal World Ruby Testing
43mInfinite Improbability Testing- Execute All Tests in Parallel
44mParallelized And Concurrent Testing With Test::Async
31mPortable and Fast - How to implement a parallel test runner
40mInfinite improbability testing – execute all tests in parallel
25mAdvanced Testing Concepts
27mParallel testing with Ractors - Putting CPU's to work
58mWays to Parallelize Tests in JavaScript