Audit automated test quality for assertion strength, boundary coverage, mock discipline, and error paths.
npx skills add https://github.com/Obsidian-Owl/specwright --skill gate-tests
Please help me install this Agent Skill. Skill: gate-tests Source: https://github.com/Obsidian-Owl/specwright/tree/main/skills/gate-tests Command: npx skills add https://github.com/Obsidian-Owl/specwright --skill gate-tests
This Skill addresses the critical issue of unreliable test suites, where passing tests provide a false sense of security because they don't effectively catch bugs. It ensures that tests are robust and meaningful.
Run the gate-tests skill to audit the quality of tests for the current work unit.
High-intent search queries and answers about installing and using this skill.
To audit automated test quality, you analyze test files for assertion strength, boundary coverage, mock discipline, and error path testing. This process delegates adversarial analysis to a dedicated agent to ensure tests provide genuine confidence in code functionality.
Adversarial analysis in test automation rigorously challenges the test suite's effectiveness to catch unreliable tests. You need this verification before merging significant code changes to ensure tests are not superficial and will actually detect regressions or critical failures.
Passing test suites fail to catch regressions due to weak assertions, poor boundary coverage, and inadequate error path testing. Auditing test quality addresses this by verifying that tests are robust, meaningful, and effective at detecting actual bugs.
Yes, you need access to project configuration and test files for comprehensive review. The audit requires these inputs to effectively analyze mock discipline, assertion strength, and boundary coverage across the codebase.
The best way to verify tests are not superficial before a merge is running an automated test quality audit. This evaluates assertion strength and error path testing, delegating adversarial analysis to ensure the suite detects regressions and provides genuine confidence.
michael-h-patriannaEnforce writing failing tests before implementing production code.
gao-hongnanAnalyze code diffs to identify missing regression coverage and brittle test patterns.
rm2thaddeusAnalyze codebases for architecture, quality, security, performance, and maintainability.
iiammaeAnalyze code coverage from fuzzing campaigns to assess harness effectiveness.
