Start with tests your team already recognises.
Repository inspection reads supported configuration and selected test files at a pinned commit. The setup proposal shows what was discovered and what remains outside the inspection. The existing-test onboarding path selects a small baseline by default, giving your team a bounded starting point to review before approving execution and its cost.
Preserve the result your framework produced.
Supported Jest, Vitest and declared command adapters retain native test evidence. The adapter approach requires its runtime and tools to be installed in the qualified runner image. Missing tools, partial reports and skipped work remain visible. Where coverage is declared, the report preserves the available native counts and identifies incomplete evidence.
- Review the detected suites and exact tested source.
- Keep failures and incomplete results attached to their run.
- Combine unit checks with approved API, property and mutation methods.
Use a baseline to plan the next checks.
A baseline can show how the selected existing tests behaved. It cannot establish that every requirement was tested or grant release readiness on its own. An evaluation reviews your framework, project layout, environment and desired scope so the first result leads to a useful next decision. Additional methods can challenge behaviours the current suite leaves unchecked.