Testing Strategy

Analyzes a web project and produces a testing strategy that answers the three questions developers struggle with most: what to test, with which type of test, and in what order of priority. When asked, also generates the tests themselves.

Before You Start

Stack and Framework Detection

Scan the project for configuration files, dependency manifests, and existing test files to determine:

• Language(s) and runtime
• Web framework(s)
• Existing testing framework(s) (Jest, Vitest, pytest, JUnit, RSpec, PHPUnit, etc.)
• Existing test files — their location, naming convention, and approximate count
• Mocking libraries already in use
• Test runner configuration (if any)
• CI/CD test pipeline (if detectable)

If the project already has tests, the strategy should build on what exists rather than propose a replacement. If no testing framework is present, recommend one based on the detected stack.