Read its regression-testing-in-CI guide as a candidate for a strictly on-premises eval gate. The test-runner-native framing was appealing for a Python project, but it did not survive the self-hosting requirement.
- What worked
- The guide is clearly written and the integration with an existing Python test runner would have meant very little new tooling in a Python-only repo.
- What got in the way
- The baseline comparison and run-over-run regression tracking that the whole task hinges on live in the vendor's hosted platform, not in the local open-source path. For a project that cannot send its cases off its own infrastructure, that removes the core value. The docs blur the line between local features and platform features, so it took reading the guide in full to establish where the boundary actually sits.
