ExplorePrabuRamaraj

Artifact file paths, naming conventions, directory structure, and JSON output schemas for QA agents. Use when writing test case files, review reports, coverage reports, or generating execution metrics JSON. Covers the complete workflow artifact directory structure and versioning rules.

BDD test step format standards for QA test case writing and review. Use when writing Given/When/Then test steps, applying 8-space indentation rules, structuring BDD scenarios, or validating BDD format compliance in test case documents.

Coverage matrix table formats, test pyramid analysis templates, and shift-left recommendation structures for QA coverage analysis and test case review. Use when producing AC coverage matrices, manual test case automation coverage tables, coverage gap analysis, shift-left recommendations, test pyramid analysis, or prioritized action plans.

Multi-source input handling for manual test case generation. Use when the input is NOT a Jira Story ID — covers User Stories, Business Flows/Processes, Use Cases, and REST API endpoint specifications. Covers input type detection, requirements extraction, reference ID generation, and test derivation rules for each source type.

Jira field extraction and validation rules for QA agents. Use when fetching Jira story details, extracting acceptance criteria using customfield_14400, mapping custom metadata fields, validating Story IDs, or reading Jira data for test case generation or coverage analysis.

Organizational test case document template and format enforcement rules. Use when generating manual test case files, formatting test case documents, writing coverage summaries, validating the organizational template structure, or ensuring compliance with the mandatory file format including header, individual test case blocks, feature toggle OFF test case, and coverage summary.

Test design technique reference for QA test engineers. Use when selecting, applying, or validating test design techniques including Equivalence Partitioning (EP), Boundary Value Analysis (BVA), Decision Table, State Transition, Use Case Testing, Error Guessing, Pairwise testing, and Input Field Validation. Covers when to use each technique and common misuse warnings.

Triage and analyze Playwright test failures. Use when: test failures need diagnosis, cross-pattern analysis of shared root causes, categorizing UI vs API failures, reading test-results/ error reports, proposing fixes for broken tests.

Guard check to confirm the summary report file exists on disk before ending a failure-analysis session. Use as the final check in step 7 of the orchestration workflow.

Generate a detailed failure analysis summary report. Use when: creating summary-report.md, documenting test fixes, generating effort savings analysis, producing iteration summaries, writing failure analysis documentation.