hoangnguyen0403/quality-engineering-quality-assurance
skills/quality-engineering/quality-engineering-quality-assurance/SKILL.md
Write manual test cases with 1-condition-per-TC granularity, Module_Action on Screen when Condition naming, platform prefix rules, and High/Normal/Low priority classification. Use when writing or reviewing manual test cases for Zephyr — to split compound TCs, fix naming violations, assign correct platform tags, or determine bug priority.
$ install --global
skillsauthnpx skillsauth add hoangnguyen0403/agent-skills-standard quality-engineering-quality-assuranceInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 20, 2026, 3:11 AM367.2s4 files scanned
SKILL.md
- name:
- quality-engineering-quality-assurance
- description:
- Write manual test cases with 1-condition-per-TC granularity, Module_Action on Screen when Condition naming, platform prefix rules, and High/Normal/Low priority classification. Use when writing or reviewing manual test cases for Zephyr — to split compound TCs, fix naming violations, assign correct platform tags, or determine bug priority.
Quality Assurance Standards
Priority: P1 (HIGH)
1. Test Case Granularity
- 1 Test Case = 1 Condition on 1 Screen.
- Split Screens: "Order Details" & "Item Details" separate.
- Split Conditions: "Config " & "Config B" separate.
- No "OR" Logic: Each TC must test single, distinct path.
2. Naming Convention
- Pattern:
Platform_Module_Action on Screen when Condition(e.g.,Web_Order_Verify...orMobile_Order_Verify...) - Rule: Only include
Web_orMobile_prefix if requirement exclusive to one platform. Omit prefix if it supports Both. - Example:
Order_Verify payment term on Item Details when Toggle is OFF(Supports Both)
3. Priority Levels
Use priority rationale to justify each classification:
- High: Critical path, blocker bug.
- Normal: Standard validation, edge case.
- Low: Cosmetic, minor improvement.
4. References
- Detailed Examples
Anti-Patterns
- No Broad TCs:
"Verify order flow works"— too broad; every TC must cover exactly 1 condition on 1 screen - No Shared TCs (Divergent): Testing Web and Mobile behavior in single TC when behavior diverges — split into separate TCs per platform
- No Incomplete Naming:
Order_Verify page— name must follow full pattern:Module_Action on Screen when Condition - No Priority Inflation: Marking cosmetic spacing bug as High priority — reserve High for critical path blockers only
Related Skills
hoangnguyen0403/common-operator-profile
testing
VerifiedTrustedCommunity
Infer the requesting operator's technical fluency from message content (never ask directly) and adapt register — business, hybrid, or technical — across SDLC workflow output. Use when starting sdlc, brainstorm-feature, plan-feature, verify-work, publish-notes, or session-report, or whenever a request's phrasing signals a non-technical or cross-stack operator.
524SKILL.mdUpdated Jul 12, 2026
hoangnguyen0403/database-transactions
documentation
VerifiedTrustedCommunity
Define transaction boundaries, locking, and consistency guarantees for multi-step writes. Use when designing atomic operations, retries, idempotency, or concurrent write behavior.
524SKILL.mdUpdated Jun 19, 2026
hoangnguyen0403/database-schema-design
development
VerifiedTrustedCommunity
Design relational or document schemas from access patterns, cardinality, and lifecycle. Use when modeling entities, choosing embed vs normalize, or shaping schema boundaries before implementation.
524SKILL.mdUpdated Jun 19, 2026
hoangnguyen0403/database-query-performance
data-ai
VerifiedTrustedCommunity
Diagnose database latency with explain plans, index ownership, and query-shape review. Use when a query is slow, an index is missing, or scans and N+1 patterns appear.
524SKILL.mdUpdated Jun 19, 2026