acm-test-case-reviewer

ACM Console UI test case review validates a test-case.md file against conventions, UI element discovery, and Acceptance Criteria. It cross-references knowledge files and uses source spot-checks to ensure test design efficiency and coverage gap verification.

Test case consistency checking covers AC vs implementation alignment, field order validation, filtering behavior, and component consistency. It also verifies functional outcome coverage to ensure the test case validates the feature's stated user outcome.

Yes, you need access to acm-source MCP and acm-knowledge-base skills to verify test cases. The acm-source MCP performs spot-checks against source code, while acm-knowledge-base provides the required conventions for validation.

You can identify test design inefficiencies by running an automated test case review. This process analyzes your test-case.md file to pinpoint design flaws and verifies coverage gaps to ensure all identified areas are fully tested.

The best way to validate Polarion metadata completeness is through an automated quality review of your test-case.md file. This enforces metadata requirements alongside UI element discovery and Acceptance Criteria consistency checks.

Test case review fails without a test-case.md file because this file is the required input for validation. The review process parses the markdown content to check conventions, AC consistency, and coverage gaps against the knowledge base.