running-tests

To automatically run tests across frameworks like Jest and Pytest, execute the runner from your project root. It detects project signals to identify the test runtime, executes the tests, and writes structured results to a JSON checkpoint.

Yes, you can use this test runner for CI-like workflows and local development automation. It provides consistent test reporting by executing discovered tests with a configurable 300-second timeout and writing structured results to .checkpoints/test-runner.json.

Framework detection for test runtimes like Cargo and Go works by analyzing project signals in your repository. The runner automatically identifies the specific test framework configured and executes the appropriate test commands without manual setup.

The timeout limit for executing tests with this automation runner is 300 seconds. If a test suite exceeds this configurable timeout, the runner stops execution and records the outcome in the structured JSON checkpoint file.

The test runner writes structured results to .checkpoints/test-runner.json. This JSON checkpoint captures the execution outcome of your discovered tests, providing reliable quality assurance data for your automation pipelines.

The best way to get structured test results without manual configuration is to run a framework-detection test runner. It automatically discovers your test runtime, executes the suite within a 300-second timeout, and outputs a structured JSON checkpoint.