qa-skills 3.0.0 → 3.1.0

package/skills/qa-testcase-from-docs/references/test-case-format.md

@@ -1,196 +0,0 @@
-# Test Case Format Reference
-
-Detailed format for test cases generated by qa-testcase-from-docs. Examples for positive, negative, boundary, and edge case types.
-
----
-
-## Standard Fields
-
-| Field | Required | Description | Example |
-| ----- | -------- | ----------- | ------- |
-| ID | Yes | Unique identifier | TC-AUTH-001 |
-| Title | Yes | Short descriptive name | Valid login with correct credentials |
-| Module | Yes | Feature/component | Authentication |
-| Priority | Yes | Critical / High / Medium / Low | High |
-| Type | Yes | positive / negative / boundary / edge | positive |
-| Preconditions | No | State before execution | User exists, account not locked |
-| Steps | Yes | Action + Expected Result table | See below |
-| Postconditions | No | State after execution | User logged in, session created |
-| Test Data | No | Input values, fixtures | email: test@example.com, password: ValidPass1! |
-| Traceability | Yes | Requirement ID(s) | REQ-FN-001 |
-
----
-
-## Steps Table
-
-| Step# | Action | Expected Result |
-| ----- | ------ | --------------- |
-| 1 | Navigate to login page | Login form displayed |
-| 2 | Enter email "test@example.com" | Email field populated |
-| 3 | Enter password "ValidPass1!" | Password masked |
-| 4 | Click "Sign In" | User redirected to dashboard |
-
-**Guidelines:**
-- One action per step
-- Expected result must be observable and verifiable
-- Avoid subjective language ("should", "might", "quickly")
-- Use specific values, not placeholders
-
----
-
-## Example: Positive Test Case
-
-```
-ID: TC-LOGIN-001
-Title: Valid login with correct credentials
-Module: Authentication
-Priority: High
-Type: positive
-Traceability: REQ-FN-001
-
-Preconditions:
-- User "test@example.com" exists with password "ValidPass1!"
-- Application is accessible
-
-Steps:
-| Step# | Action | Expected Result |
-| ----- | ------ | --------------- |
-| 1 | Open application login page | Login form displayed |
-| 2 | Enter "test@example.com" in email field | Email field shows entered value |
-| 3 | Enter "ValidPass1!" in password field | Password masked with dots |
-| 4 | Click "Sign In" button | User redirected to dashboard |
-| 5 | Verify dashboard loads | Dashboard displays user name and menu |
-
-Postconditions:
-- User session active
-- Session cookie set
-
-Test Data: email=test@example.com, password=ValidPass1!
-```
-
----
-
-## Example: Negative Test Case
-
-```
-ID: TC-LOGIN-002
-Title: Login fails with incorrect password
-Module: Authentication
-Priority: High
-Type: negative
-Traceability: REQ-FN-001
-
-Preconditions:
-- User "test@example.com" exists
-- Application is accessible
-
-Steps:
-| Step# | Action | Expected Result |
-| ----- | ------ | --------------- |
-| 1 | Open application login page | Login form displayed |
-| 2 | Enter "test@example.com" in email field | Email field shows entered value |
-| 3 | Enter "WrongPassword123" in password field | Password masked |
-| 4 | Click "Sign In" button | Error message: "Invalid email or password" |
-| 5 | Verify user remains on login page | No redirect, form still visible |
-| 6 | Verify no session created | No session cookie set |
-
-Postconditions:
-- User not logged in
-- Failed attempt logged (if applicable)
-
-Test Data: email=test@example.com, password=WrongPassword123
-```
-
----
-
-## Example: Boundary Test Case
-
-```
-ID: TC-LOGIN-003
-Title: Login with minimum valid password length (8 characters)
-Module: Authentication
-Priority: Medium
-Type: boundary
-Traceability: REQ-FN-001
-
-Preconditions:
-- User "test@example.com" exists with password "Abcd1234" (exactly 8 chars)
-- Application is accessible
-
-Steps:
-| Step# | Action | Expected Result |
-| ----- | ------ | --------------- |
-| 1 | Open application login page | Login form displayed |
-| 2 | Enter "test@example.com" in email field | Email field shows entered value |
-| 3 | Enter "Abcd1234" in password field | Password accepted (8 chars = min valid) |
-| 4 | Click "Sign In" button | User redirected to dashboard |
-
-Postconditions:
-- User logged in successfully
-
-Test Data: email=test@example.com, password=Abcd1234 (length=8)
-```
-
----
-
-## Example: Edge Case Test Case
-
-```
-ID: TC-LOGIN-004
-Title: Login with optional "Remember me" unchecked (default state)
-Module: Authentication
-Priority: Low
-Type: edge
-Traceability: REQ-FN-001
-
-Preconditions:
-- User exists
-- Application is accessible
-- "Remember me" is optional and unchecked by default
-
-Steps:
-| Step# | Action | Expected Result |
-| ----- | ------ | --------------- |
-| 1 | Open application login page | Login form displayed, "Remember me" unchecked |
-| 2 | Enter valid credentials | Fields populated |
-| 3 | Leave "Remember me" unchecked | No change to default |
-| 4 | Click "Sign In" button | User logged in |
-| 5 | Close browser completely | Browser closed |
-| 6 | Reopen application | User prompted to login (session not persisted) |
-
-Postconditions:
-- Session was non-persistent (session cookie, not persistent)
-```
-
----
-
-## JSON Structure (Export Format)
-
-```json
-{
-  "id": "TC-LOGIN-001",
-  "title": "Valid login with correct credentials",
-  "module": "Authentication",
-  "priority": "High",
-  "type": "positive",
-  "traceability": ["REQ-FN-001"],
-  "preconditions": "User exists, application accessible",
-  "steps": [
-    { "step": 1, "action": "Open application login page", "expectedResult": "Login form displayed" },
-    { "step": 2, "action": "Enter valid email", "expectedResult": "Email field populated" }
-  ],
-  "postconditions": "User session active",
-  "testData": { "email": "test@example.com", "password": "ValidPass1!" }
-}
-```
-
----
-
-## CSV Structure (Export Format)
-
-```csv
-ID,Title,Module,Priority,Type,Preconditions,Steps,Postconditions,Test Data,Traceability
-TC-LOGIN-001,Valid login with correct credentials,Authentication,High,positive,"User exists","1. Open login page|2. Enter credentials|3. Click Sign In","User logged in","email=test@example.com","REQ-FN-001"
-```
-
-Note: Steps may use `|` or `;` as delimiter within the cell; format depends on target tool.

package/skills/qa-testcase-from-docs/references/test-design-techniques.md

@@ -1,126 +0,0 @@
-# ISO 29119-4 Test Design Techniques
-
-Test design techniques per ISO/IEC/IEEE 29119-4. Use these to build test models and derive test cases with measurable coverage.
-
----
-
-## Equivalence Partitioning (EP)
-
-**Description:** Partition input domain into equivalence classes where members are expected to behave identically. Select one representative from each partition to reduce test count while maintaining coverage.
-
-**When to use:** Input fields with ranges, sets of valid/invalid values, enumerated types, validation rules.
-
-**Example:** Password field (8–128 chars)
-- Partition 1: Valid (8–128 chars) → pick 12 chars
-- Partition 2: Too short (< 8) → pick 5 chars
-- Partition 3: Too long (> 128) → pick 130 chars
-- Partition 4: Empty → empty string
-- Partition 5: Null (if applicable) → null
-
-**Coverage:** At least one test per partition.
-
----
-
-## Boundary Value Analysis (BVA)
-
-**Description:** Test at and around boundaries of input domains. Defects often occur at min, max, and off-by-one values.
-
-**When to use:** Numeric ranges, string lengths, array sizes, pagination limits, date ranges.
-
-**Example:** Age field (18–120)
-- Min boundary: 18 (valid)
-- Min - 1: 17 (invalid)
-- Max boundary: 120 (valid)
-- Max + 1: 121 (invalid)
-- Typical: 25 (valid)
-
-**Coverage:** Min, min-1, max, max+1, and optionally typical value per boundary.
-
----
-
-## Decision Tables
-
-**Description:** Tabular representation of business rules. Rows = rule combinations, columns = conditions and actions. Each row yields a test case.
-
-**When to use:** Multiple conditions affecting outcome, business rules, discount/eligibility logic, access control.
-
-**Example:** Login (2FA enabled/disabled, valid/invalid password)
-
-| 2FA Enabled | Password Valid | Expected |
-| ----------- | -------------- | -------- |
-| No | Yes | Login success |
-| No | No | Error: invalid password |
-| Yes | Yes | Prompt for 2FA code |
-| Yes | No | Error: invalid password |
-
-**Coverage:** One test per rule (row). Consider all combinations or use techniques to reduce (e.g., pairwise) if combinatorial explosion.
-
----
-
-## State Transition Testing
-
-**Description:** Model system as states and transitions. Test paths through the state machine: all states, all transitions, or specific paths (e.g., happy path, error paths).
-
-**When to use:** Workflows, lifecycles, multi-step processes, order status, user sessions, wizards.
-
-**Example:** Order lifecycle: Draft → Submitted → Paid → Shipped → Delivered
-
-- States: Draft, Submitted, Paid, Shipped, Delivered, Cancelled
-- Transitions: submit, pay, ship, deliver, cancel
-- Test paths: Draft→Submitted→Paid→Shipped→Delivered; Draft→Cancelled; invalid transitions (e.g., Paid→Draft)
-
-**Coverage:** All states, all transitions, or transition pairs (0-switch, 1-switch coverage).
-
----
-
-## Use Case Testing
-
-**Description:** Derive test scenarios from use cases. Cover main success scenario, extensions (alternate flows), and exception flows.
-
-**When to use:** User-facing features, documented use cases, user stories with Given/When/Then.
-
-**Example:** Use case "Place Order"
-- Main: Add items → Enter shipping → Pay → Order confirmed
-- Extension 2a: Apply discount code
-- Extension 3a: Save for later
-- Exception 2b: Invalid payment → retry or cancel
-
-**Coverage:** Main scenario + each extension + each exception.
-
----
-
-## Classification Trees
-
-**Description:** Hierarchical decomposition of test object into classifications and classes. Combine classes across classifications to form test cases.
-
-**When to use:** Complex objects with multiple attributes, configuration testing, combinatorial selection.
-
-**Example:** Search filters: Category (Electronics, Clothing, Books), Price (Low, Mid, High), Sort (Relevance, Price, Date)
-
-- Classes: 3 × 3 × 3 = 27 combinations
-- Use pairwise or risk-based selection to reduce
-
-**Coverage:** All classes exercised; combination coverage as defined (full, pairwise, etc.).
-
----
-
-## Technique Selection Guide
-
-| Situation | Preferred Technique(s) |
-| --------- | ---------------------- |
-| Input validation | EP, BVA |
-| Business rules | Decision tables |
-| Workflows, lifecycles | State transition |
-| User flows | Use case testing |
-| Complex combinations | Classification trees, decision tables |
-| API parameters | EP, BVA |
-| Form fields | EP, BVA, decision tables (for conditional validation) |
-
----
-
-## Combining Techniques
-
-Often combine techniques for full coverage:
-- **EP + BVA:** Partition first, then add boundary tests
-- **State + Use case:** Model workflow as state machine, derive scenarios from use case
-- **Decision table + EP:** Rules define partitions, EP refines input selection

package/skills/qa-testcase-from-docs/templates/test-case-template.md

@@ -1,31 +0,0 @@
-# Test Case
-
-## [TC-{ID}] {Title}
-
-**Module:** {module name}
-**Priority:** {P1 | P2 | P3 | P4}
-**Type:** {Functional | Regression | Smoke | Integration | E2E | Other}
-
-## Preconditions
-{Prerequisites, data state, environment setup}
-
-## Test Steps
-
-| # | Action | Expected Result |
-|---|--------|-----------------|
-| 1 | {action} | {expected} |
-| 2 | {action} | {expected} |
-| 3 | {action} | {expected} |
-
-## Postconditions
-{Cleanup, state after test}
-
-## Test Data
-{Input values, test accounts, sample data}
-
-## Traceability
-- **Requirement ID:** [REQ-{ID}]
-- **Spec Reference:** {section or link}
-
-## Automation Status
-{Manual | Automated | Planned | N/A}

package/skills/qa-testcase-from-ui/SKILL.md

@@ -1,109 +0,0 @@
----
-name: qa-testcase-from-ui
-description: Generate test cases from screenshots, UI mockups, and Figma exports using vision analysis to identify interactive elements and derive test scenarios.
-output_dir: test-cases/from-ui
-dependencies:
-  recommended:
-    - qa-browser-data-collector
----
-
-# QA Test Case from UI
-
-## Purpose
-
-Generate UI-specific test cases from visual representations of interfaces. Use vision analysis to identify interactive elements, infer user actions, and produce structured test scenarios with visual references (element descriptions, coordinates) for manual or automated testing.
-
-## Trigger Phrases
-
-- "Generate test cases from this screenshot" / "Create tests from UI image"
-- "Test cases from Figma export" / "Tests from mockup"
-- "Analyze this wireframe and write test scenarios"
-- "UI test cases from [screenshot/mockup/wireframe]"
-- "Identify interactive elements and create test cases"
-- "Vision-based test case generation" / "Visual UI testing scenarios"
-
-## Input Types
-
-| Type | Formats | Notes |
-|------|---------|-------|
-| **Screenshots** | PNG, JPG, WebP | Live app captures, design exports |
-| **Figma exports** | PNG, SVG, PDF | Design-to-test workflow |
-| **UI mockups** | PNG, JPG | Static design comps |
-| **Wireframes** | PNG, PDF | Low-fidelity layouts |
-
-## Vision Analysis Workflow
-
-1. **Accept image paths** — User provides one or more image file paths
-2. **Identify UI elements** — Detect fields, buttons, tables, modals, forms, navigation, links, icons
-3. **Semantic mapping** — Infer possible user actions from context (labels, layout, conventions)
-4. **Generate UI test scenarios** — Produce scenarios covering navigation, forms, validation, responsiveness, edge cases
-
-## Test Scenario Categories
-
-| Category | Examples |
-|----------|----------|
-| **Form interactions** | Input, validation, submission, reset |
-| **Navigation flows** | Menu, breadcrumbs, tabs, links |
-| **Modal/dialog interactions** | Open, close, confirm, cancel |
-| **Table/list operations** | Sort, filter, pagination, row actions |
-| **Responsive layout** | Breakpoints, overflow, touch targets |
-| **Error states** | Validation messages, empty states |
-| **Loading states** | Spinners, skeletons, disabled states |
-| **Accessibility** | Focus order, labels, contrast |
-
-## Output Format
-
-Test cases include visual references for traceability:
-
-```markdown
-## TC-UI-001: Login form submission
-**Visual ref:** Login form, center of screen (~50%, 40%)
-**Elements:** Email input, Password input, "Sign In" button
-
-| Step | Action | Expected Result |
-|------|--------|-----------------|
-| 1 | Enter valid email in Email field | Value accepted |
-| 2 | Enter valid password | Value masked |
-| 3 | Click "Sign In" | Redirect to dashboard |
-```
-
-## Scope
-
-**Can do (autonomous):**
-- Analyze provided image paths for UI elements
-- Identify common patterns (forms, buttons, tables, modals, nav)
-- Generate test scenarios with element descriptions
-- Infer semantic actions from labels and layout
-- Produce structured output (tables, Gherkin, or project format)
-- Reference `references/ui-element-patterns.md` and `references/visual-analysis-guide.md`
-
-**Cannot do (requires confirmation):**
-- Access images without explicit paths
-- Assume element behavior not visible in image
-- Generate assertions for dynamic behavior (e.g., API responses) without context
-
-**Will not do (out of scope):**
-- Execute tests or interact with live applications
-- Modify source images or designs
-- Generate test code (hand off to qa-playwright-ts-writer or similar)
-
-## Quality Checklist
-
-- [ ] All visible interactive elements identified
-- [ ] Test scenarios map to inferred user actions
-- [ ] Visual references included (element descriptions, approximate location)
-- [ ] Categories cover forms, navigation, modals, tables, states
-- [ ] Edge cases considered (empty, invalid, loading)
-- [ ] Output format matches project convention
-- [ ] No assumptions about backend behavior without context
-
-## Troubleshooting
-
-| Symptom | Likely Cause | Fix |
-|---------|--------------|-----|
-| Elements not identified | Low resolution, overlapping UI | Ask for higher-res image or zoomed crop |
-| Wrong element type inferred | Ambiguous visual design | Use conservative labels; flag for review |
-| Too many/too few scenarios | Scope unclear | Ask user for priority (smoke vs full coverage) |
-| Coordinates inaccurate | Vision model variance | Use semantic descriptions over coordinates |
-| Figma export differs from screenshot | Design vs implementation gap | Note "design intent"; suggest live capture for implementation tests |
-| Non-interactive elements flagged | Decorative elements look clickable | Apply visual-analysis-guide heuristics |

package/skills/qa-testcase-from-ui/references/ui-element-patterns.md

@@ -1,126 +0,0 @@
-# UI Element Patterns and Test Scenarios
-
-Common UI element patterns and their associated test scenarios. Use this reference when generating test cases from visual UI analysis.
-
----
-
-## Forms
-
-| Element | Visual Cues | Test Scenarios |
-|---------|-------------|----------------|
-| **Text input** | Rectangular field, placeholder/label | Valid input, empty submit, max length, special chars, paste |
-| **Password input** | Masked dots, "show/hide" toggle | Valid password, empty, strength indicator, show/hide toggle |
-| **Email input** | Label "Email", @ in placeholder | Valid format, invalid format, duplicate, empty |
-| **Textarea** | Multi-line box | Valid text, resize, max chars, line breaks |
-| **Checkbox** | Square, checked/unchecked | Toggle on/off, required unchecked, multiple selection |
-| **Radio group** | Circles, one selected | Select option, required unselected, change selection |
-| **Select/Dropdown** | Arrow, single visible value | Open, select option, keyboard nav, empty option |
-| **Multi-select** | Chips/tags, "x" to remove | Add, remove, select all, clear all |
-| **Date picker** | Calendar icon, date format | Select date, invalid date, past/future constraints |
-| **File upload** | "Choose file" / drag zone | Valid file, invalid type, size limit, multiple files |
-| **Submit button** | Primary CTA, often bottom-right | Click submit, disabled when invalid, loading state |
-
-**Form-level scenarios:** Required field validation, inline vs on-submit validation, reset/clear, tab order, error message display.
-
----
-
-## Buttons
-
-| Type | Visual Cues | Test Scenarios |
-|------|-------------|----------------|
-| **Primary** | Filled, prominent color | Click action, disabled state, loading spinner |
-| **Secondary** | Outline or muted | Click action, consistency with primary |
-| **Destructive** | Red/danger color | Confirmation flow, cancel option |
-| **Icon button** | Icon only, optional tooltip | Click, keyboard, tooltip on hover |
-| **Link-styled** | Underlined text, cursor pointer | Navigate, open in new tab, disabled |
-
----
-
-## Dropdowns
-
-| Pattern | Visual Cues | Test Scenarios |
-|---------|-------------|----------------|
-| **Single select** | One value shown, chevron | Open, select, close on outside click, keyboard |
-| **Multi-select** | Chips/tags | Add, remove, select all, search/filter |
-| **Cascading** | Parent selection enables child | Parent change clears child, dependent options |
-| **Searchable** | Input inside dropdown | Type to filter, no results state |
-| **Grouped options** | Section headers | Navigate groups, select from group |
-
----
-
-## Modals / Dialogs
-
-| Pattern | Visual Cues | Test Scenarios |
-|---------|-------------|----------------|
-| **Confirmation** | Title, message, OK/Cancel | Confirm, cancel, ESC key, backdrop click |
-| **Form modal** | Form inside overlay | Submit, cancel, validation, focus trap |
-| **Alert** | Icon, message, single button | Dismiss, auto-close (if applicable) |
-| **Full-screen modal** | Overlay covers viewport | Close button, ESC, scroll behavior |
-
-**Common scenarios:** Focus trapped inside, focus returns on close, scroll lock on body, aria attributes.
-
----
-
-## Tables
-
-| Element | Visual Cues | Test Scenarios |
-|---------|-------------|----------------|
-| **Sortable columns** | Header arrows/icons | Sort asc/desc, multi-column sort |
-| **Row actions** | Icons/buttons per row | Edit, delete, expand, bulk select |
-| **Pagination** | Page numbers, prev/next | Navigate pages, change page size |
-| **Filter** | Input above table | Filter by column, clear filter |
-| **Empty state** | "No data" message | Display when no rows |
-| **Loading** | Skeleton or spinner | Display during fetch |
-
----
-
-## Navigation Bars
-
-| Pattern | Visual Cues | Test Scenarios |
-|---------|-------------|----------------|
-| **Top nav** | Horizontal links, logo | Click each link, active state, responsive collapse |
-| **Sidebar** | Vertical menu | Expand/collapse, nested items, active state |
-| **Breadcrumbs** | Path: Home > Section > Page | Click each level, truncation |
-| **Mega menu** | Hover reveals panel | Hover, click sub-items, keyboard nav |
-
----
-
-## Tabs
-
-| Pattern | Visual Cues | Test Scenarios |
-|---------|-------------|----------------|
-| **Horizontal tabs** | Underline or pill for active | Switch tabs, keyboard (arrow keys) |
-| **Vertical tabs** | Side panel | Same as horizontal |
-| **Scrollable tabs** | Overflow with arrows | Scroll, select from overflow |
-| **Add/close tabs** | "+" or "x" on tab | Add tab, close tab, close last tab |
-
----
-
-## Tooltips
-
-| Pattern | Visual Cues | Test Scenarios |
-|---------|-------------|----------------|
-| **Hover tooltip** | Small popover on hover | Appear on hover, disappear on leave |
-| **Focus tooltip** | Appears on focus | Keyboard focus, dismiss |
-| **Rich tooltip** | Multi-line, links | Content display, link click |
-
----
-
-## Notifications
-
-| Pattern | Visual Cues | Test Scenarios |
-|---------|-------------|----------------|
-| **Toast** | Corner popup, auto-dismiss | Appear, auto-close, manual dismiss |
-| **Inline alert** | Banner above/below content | Dismiss, persist until action |
-| **Badge** | Count on icon (e.g., cart) | Display count, click navigates |
-| **Status indicator** | Dot or icon (success/error) | Correct color for state |
-
----
-
-## Cross-Cutting Scenarios
-
-- **Responsive:** Element visibility at breakpoints, touch target size, overflow
-- **Loading:** Skeleton, spinner, disabled state during async
-- **Error:** Validation message placement, retry option
-- **Empty:** Empty state message, CTA when no data
-- **Accessibility:** Focus order, aria-labels, keyboard navigation