test-pattern-analysis

Test pattern analysis examines your test files across frameworks like pytest, jest, go, junit, and rspec to surface reusable fixtures, naming conventions, and structural patterns (AAA, Given-When-Then). The Skill parses your tests and emits a standardized report identifying these patterns for consistent test development.

Pattern analysis works across pytest, jest, go, junit, and rspec frameworks. It detects the framework in use, extracts fixtures and utilities specific to each, and identifies common conventions and structure patterns regardless of which framework your codebase employs.

Yes. The Skill extracts naming conventions and test structure patterns from your existing suite, then suggests improvements and consistent standards. This helps teams align on fixture names, test case naming, and utility conventions across their test codebase.

The analysis generates a standardized JSON report saved to bazinga/artifacts/{SESSION_ID}/skills/test_patterns.json containing extracted fixtures, naming conventions, detected patterns (AAA, Given-When-Then), utilities, and suggested improvements for your test suite.

By surfacing reusable fixtures, utilities, and conventions already present in your tests, pattern analysis eliminates duplicate setup code and inconsistent naming. Teams can apply identified patterns to new tests, reducing development time and improving test maintainability.