quality-engineering-quality-assurance skillA
quality-engineering-quality-assurance is agent-read markdown (skill) from hoangnguyen0403/agent-skills-standard: Write or review manual Zephyr 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 for test-case authoring and review; defer Jira traceability, linking, and pushing cases to Zephyr..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# 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...` or `Mobile_Order_Verify...`) - **Rule**: Only include `Web_` or `Mobile_` 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](references/test_case_standards.md) ## Anti-Patterns - **No Broad TCs**: `"Verify order flow works"` — too broad; every TC must cover exactly 1 condition on 1 screen …
Read the whole file at its exact version.
How to install
mdr add hoangnguyen0403/agent-skills-standard/quality-engineering-quality-assurance@git:20260821.b9b1ba0mdr add hoangnguyen0403/agent-skills-standard/quality-engineering-quality-assurance@sha256:a0e544a5cf83c25aPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_ghvzuuxmzewpnadi)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2524 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
hoangnguyen0403/agent-skills-standard · 571 stars · license MIT · pushed 2026-09-24 · branch develop
API
GET https://markdownregistry.com/api/v1/artifacts/art_ghvzuuxmzewpnadi GET https://markdownregistry.com/api/v1/resolve?ref=hoangnguyen0403/agent-skills-standard/quality-engineering-quality-assurance GET https://markdownregistry.com/api/v1/blob/a0e544a5cf83c25a88a9a6c36adb8cf2badb1d2537d8c33ed0761ed700255267
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from hoangnguyen0403/agent-skills-standard
Every file in hoangnguyen0403/agent-skills-standard