Home / Use cases
Where rpytest earns its keep
rpytest pays off wherever the same suite is invoked many times and the interpreter, plugins, and collection would otherwise be re-paid on every run. These are the jobs the daemon model was built for.
Developer workflow
The TDD inner loop
Cut the save-run-read cycle from seconds to a fast RPC by keeping the interpreter and collection warm.
Read the walkthrough → Continuous integrationCI test hot paths
Drop fixed per-invocation cost from retries, last-failed reruns, and shards without adding a plugin dependency.
Read the walkthrough → ScaleLarge suites with heavy plugins
Amortise expensive collection and plugin import once per session for suites where collection dominates wall clock.
Read the walkthrough →