Testing configured

Severity: Critical

Check for test framework configuration:

# Look for test config files
ls -la jest.config.* vitest.config.* pytest.ini pyproject.toml setup.cfg 2>/dev/null

# Check package.json for test script
grep -A2 '"test"' package.json 2>/dev/null

Check CI config for test commands:

grep -r -E "(jest|vitest|pytest|rspec|go test|npm test|pnpm test|yarn test|make test)" .github/workflows/ 2>/dev/null

Verify tests run on PRs (check workflow triggers):

grep -A5 "on:" .github/workflows/*.yml | grep -E "(pull_request|push)"

Test locally:

1. Find test command in package.json scripts, Makefile, or CI config
2. Run it: npm test, pnpm test, pytest, etc.
3. Note if tests pass, fail, or error out

Pass criteria:

• Test framework is configured locally
• Test command is discoverable (package.json, Makefile, or README)
• CI includes test execution step
• Tests run on pull requests (not just main/staging)
• Tests run locally without erroring out

Fail criteria:

• No test framework configured
• No test step in CI
• Tests only run on main (not on PRs)
• Test command crashes or is misconfigured

Evidence to capture:

• Test framework used
• Test config file location
• Workflow triggers (confirms PR coverage)
• Local test output (pass/fail count, any errors)
• Test coverage percentage if available

---