Skip to content
cccskills
FreePublished on GitHub

quality-engineering-quality-assurance

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.

The English summary is being prepared. Showing the original description.

Works withJira

Run score Not tested

See how to install

Files included (4)

  • SKILL.md2.5 KB
  • evals/evals.json3.0 KB
  • references/TDD_FEEDBACK.md942 B
  • references/test_case_standards.md1.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

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

Review wording

  • Call out naming violations explicitly when a test case breaks the naming convention, then split it into separate TCs with one condition on one screen.

Canonical response anchors

When this skill applies, preserve the following domain terminology or equivalent concrete examples in the answer when relevant:

  • naming violations
  • 1 Test Case = 1 Condition
  • High: Critical path
  • Low: Cosmetic
  • Module_Action on Screen when Condition
  • No "OR" Logic
  • Split into separate TCs
  • priority rationale

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Upgrade an Android project to Android Gradle Plugin (AGP) 9. Use when migrating to AGP 9, updating Gradle build files, migrating to built-in Kotlin, or adopting the new AGP DSL.

The English summary is being prepared. Showing the original description.

HoangNguyen0403/agent-skills-standard581Updated Oct 24, 2026

Apply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns; defer Compose state and ViewModel/StateFlow implementation to their specific skills.

The English summary is being prepared. Showing the original description.

HoangNguyen0403/agent-skills-standard581Updated Oct 24, 2026

Implement WorkManager and background processing correctly on Android. Use when creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, or setting up Hilt in workers; defer FCM and notification delivery to android-notifications.

The English summary is being prepared. Showing the original description.

HoangNguyen0403/agent-skills-standard581Updated Oct 24, 2026

Build high-performance declarative UI with Jetpack Compose. Use when writing Composable functions, optimizing recomposition, hoisting state, or working with LazyColumn and side effects; defer deep-link and navigation routing to android-navigation.

The English summary is being prepared. Showing the original description.

HoangNguyen0403/agent-skills-standard581Updated Oct 24, 2026

Migrate an Android XML View to Jetpack Compose following a structured 10-step workflow. Use when converting XML layouts to Compose, setting up Compose in an existing View-based project, or incrementally adopting Compose.

The English summary is being prepared. Showing the original description.

HoangNguyen0403/agent-skills-standard581Updated Oct 24, 2026

Write correct coroutine scopes, lifecycle collection, and dispatcher injection in Android production code. Use for suspend functions, coroutine scopes, and dispatcher mechanics; defer ViewModel StateFlow/LiveData architecture, Fragment lifecycle recipes, persistence/notifications, and unit-test recipes to their specific skills.

The English summary is being prepared. Showing the original description.

HoangNguyen0403/agent-skills-standard581Updated Oct 24, 2026

See all skills by HoangNguyen0403

Report a problem with this skill