learning-test-theater-patterns

You can discover weak or missing tests from project retrospectives by mining post-mortems, tech-debt reports, and task updates to surface candidate test theater patterns. The extracted patterns include source attribution for review before merging into the library.

Test theater patterns are testing gaps and antipatterns found in project artifacts. You identify them by analyzing documentation like retrospectives and post-mortems to extract mentions of missed tests, generating candidates for review.

To extract test antipatterns without duplication, scan post-mortems for testing gaps and check candidates against the existing pattern library. The system surfaces patterns respecting current references and requires user approval before adding new entries.

Yes, you can use documentation review to find test coverage gaps by analyzing tech-debt reports. The process mines these artifacts to surface candidate test theater patterns, presenting them with source metadata for your approval.

Yes, the pattern discovery process requires manual approval before updating the pattern library. It presents candidate test theater patterns with source attribution and records metadata, ensuring no changes occur without explicit user review.

The best way to analyze repository artifacts for testing antipatterns is to mine post-mortems, retrospectives, and tech-debt reports for testing gaps. This surfaces candidate patterns with traceability metadata for user review and library integration.