Get the latest tech news
Why Rust nextest is process-per-test
Why nextest runs each test in its own process: a game-theoretic view.
Consider this classic problem: if two people need to meet in London on a particular day but can’t coordinate the time and place, they’re likely to choose noon at Big Ben. Process-per-test makes these valuable patterns harder to achieve: semaphores must be managed by the test runner, in-memory state must be stored on disk, and shared servers must live out-of-process. We’ll consider opt-ins for newer patterns that can deliver feature-rich and reliable test running at scale like nextest does today.
Or read this on Hacker News