ai-qakit 1.0.0

package/templates/.claude/commands/qakit/docs/capture-test-knowledge.md

@@ -0,0 +1,451 @@
+# Capture Test Knowledge
+
+Analyze test architecture and generate comprehensive documentation with visual diagrams.
+
+## Usage
+
+```
+/qakit:docs/capture-test-knowledge [entry-point]
+```
+
+## Options
+
+| Entry Point | Description |
+|-------------|-------------|
+| `file-path` | Analyze specific test file |
+| `folder-path` | Analyze test folder/module |
+| `page-object` | Analyze Page Object class |
+| `fixture` | Analyze test fixtures |
+| `flow` | Analyze E2E test flow |
+
+## Examples
+
+```bash
+/qakit:docs/capture-test-knowledge tests/e2e/checkout/
+/qakit:docs/capture-test-knowledge pages/LoginPage.ts
+/qakit:docs/capture-test-knowledge "user registration flow"
+/qakit:docs/capture-test-knowledge fixtures/auth.fixture.ts
+```
+
+## Instructions
+
+### Step 1: Gather Context
+
+Ask user for:
+
+**Question 1: Entry Point**
+- What test code do you want to document?
+- Options: Test file, Test folder, Page Object, Fixture, Test flow
+
+**Question 2: Purpose**
+- Why are you capturing this knowledge?
+- Options: Onboarding, Documentation, Refactoring, Knowledge transfer
+
+**Question 3: Depth**
+- How deep should the analysis go?
+- Options: Surface, Standard, Deep, Exhaustive
+
+### Step 2: Detect Test Framework
+
+Identify framework and structure:
+
+```bash
+# Check for framework configs
+ls -la playwright.config.* wdio.*.conf.* cypress.config.* 2>/dev/null
+
+# Find test files
+find . -name "*.spec.ts" -o -name "*.test.ts" | head -20
+
+# Find page objects
+find . -path "*/pages/*" -name "*.ts" | head -20
+```
+
+### Step 3: Analyze Test Architecture
+
+**For Test Files:**
+- Test suites and cases
+- Dependencies (Page Objects, fixtures)
+- Test data sources
+- Hooks (beforeAll, beforeEach, etc.)
+
+**For Page Objects:**
+- Selectors and locators
+- Action methods
+- Assertion helpers
+- Inheritance chain
+
+**For Fixtures:**
+- Data structures
+- Setup/teardown logic
+- Shared state management
+
+**For Test Flows:**
+- Step sequence
+- Page transitions
+- Data flow
+- Error handling
+
+### Step 4: Build Dependency Graph
+
+```bash
+# Find imports in test files
+grep -E "^import|from" [file-path]
+
+# Find Page Object usage
+grep -rn "new.*Page\|Page\." tests/
+
+# Find fixture usage
+grep -rn "useFixture\|fixtures\." tests/
+```
+
+### Step 5: Generate Documentation
+
+Create: `docs/test-knowledge-{name}.md`
+
+```markdown
+# Test Knowledge: [Entry Point Name]
+
+> Auto-generated test architecture documentation
+> Generated: [date]
+
+## Overview
+
+[Purpose and high-level description of this test module]
+
+## Entry Point
+
+- **Type:** [Test File / Page Object / Fixture / Flow]
+- **Path:** `[path]`
+- **Framework:** [Playwright / WebdriverIO / Cypress]
+
+## Test Architecture
+
+### Test Structure
+
+```
+[folder-name]/
+├── specs/           # Test specifications
+│   ├── login.spec.ts
+│   └── checkout.spec.ts
+├── pages/           # Page Objects
+│   ├── BasePage.ts
+│   └── LoginPage.ts
+├── fixtures/        # Test data & setup
+│   └── auth.fixture.ts
+└── helpers/         # Utility functions
+    └── api.helper.ts
+```
+
+### Component Diagram
+
+```mermaid
+graph TB
+    subgraph Tests
+        T1[login.spec.ts]
+        T2[checkout.spec.ts]
+    end
+    
+    subgraph Pages
+        P1[LoginPage]
+        P2[CheckoutPage]
+        P0[BasePage]
+    end
+    
+    subgraph Fixtures
+        F1[auth.fixture]
+        F2[data.fixture]
+    end
+    
+    T1 --> P1
+    T2 --> P2
+    P1 --> P0
+    P2 --> P0
+    T1 --> F1
+    T2 --> F2
+```
+
+## Test Cases
+
+| Test Suite | Test Case | Priority | Status |
+|------------|-----------|----------|--------|
+| Login | Valid credentials | P0 | ✅ |
+| Login | Invalid password | P1 | ✅ |
+| Login | Empty fields | P1 | ✅ |
+
+## Page Objects
+
+### [PageName]
+
+**File:** `pages/[PageName].ts`
+
+**Selectors:**
+| Name | Locator | Purpose |
+|------|---------|---------|
+| usernameInput | `[data-testid="username"]` | Username field |
+| passwordInput | `[data-testid="password"]` | Password field |
+| submitButton | `[data-testid="submit"]` | Login button |
+
+**Methods:**
+| Method | Parameters | Returns | Description |
+|--------|------------|---------|-------------|
+| login | email, password | void | Perform login |
+| getErrorMessage | - | string | Get error text |
+
+**Class Diagram:**
+
+```mermaid
+classDiagram
+    class BasePage {
+        +page: Page
+        +navigate(url)
+        +waitForLoad()
+    }
+    
+    class LoginPage {
+        +usernameInput: Locator
+        +passwordInput: Locator
+        +submitButton: Locator
+        +login(email, password)
+        +getErrorMessage()
+    }
+    
+    BasePage <|-- LoginPage
+```
+
+## Test Flow
+
+### [Flow Name]
+
+```mermaid
+sequenceDiagram
+    participant Test
+    participant LoginPage
+    participant API
+    participant Database
+    
+    Test->>LoginPage: navigate()
+    Test->>LoginPage: login(email, password)
+    LoginPage->>API: POST /auth/login
+    API->>Database: Validate credentials
+    Database-->>API: User data
+    API-->>LoginPage: Auth token
+    LoginPage-->>Test: Success
+```
+
+### Flow Steps
+
+1. **Setup** - Create test user via API
+2. **Navigate** - Go to login page
+3. **Action** - Enter credentials and submit
+4. **Verify** - Check redirect and session
+5. **Cleanup** - Delete test user
+
+## Fixtures & Test Data
+
+### [Fixture Name]
+
+**File:** `fixtures/[name].fixture.ts`
+
+**Data Structure:**
+```typescript
+interface UserFixture {
+  email: string;
+  password: string;
+  role: 'admin' | 'user';
+}
+```
+
+**Usage:**
+```typescript
+test.use({ storageState: 'auth.json' });
+
+test('with auth', async ({ authenticatedPage }) => {
+  // User is already logged in
+});
+```
+
+## Dependencies
+
+### Internal Dependencies
+
+| Module | Purpose | Used By |
+|--------|---------|---------|
+| BasePage | Common page methods | All pages |
+| ApiHelper | API utilities | Fixtures |
+| TestData | Data generators | All tests |
+
+### External Dependencies
+
+| Package | Version | Purpose |
+|---------|---------|---------|
+| @playwright/test | 1.42.0 | Test framework |
+| faker | 8.4.0 | Test data generation |
+| dotenv | 16.4.0 | Environment config |
+
+### Dependency Graph
+
+```mermaid
+graph LR
+    subgraph Tests
+        A[login.spec.ts]
+    end
+    
+    subgraph Pages
+        B[LoginPage]
+        C[BasePage]
+    end
+    
+    subgraph Fixtures
+        D[auth.fixture]
+    end
+    
+    subgraph External
+        E[@playwright/test]
+        F[faker]
+    end
+    
+    A --> B
+    A --> D
+    B --> C
+    B --> E
+    D --> F
+```
+
+## Quality Analysis
+
+### Test Coverage
+
+| Area | Covered | Total | Percentage |
+|------|---------|-------|------------|
+| Happy paths | 8 | 8 | 100% |
+| Error cases | 5 | 8 | 62% |
+| Edge cases | 3 | 6 | 50% |
+
+### Code Quality
+
+- **Page Object Pattern:** ✅ Properly implemented
+- **Test Independence:** ✅ No shared state
+- **Explicit Waits:** ⚠️ 2 hard waits found
+- **Data Management:** ✅ Using fixtures
+
+### Identified Issues
+
+| Issue | Severity | Location | Recommendation |
+|-------|----------|----------|----------------|
+| Hard wait | 🟠 Major | line 45 | Use explicit wait |
+| Missing cleanup | 🟡 Minor | afterEach | Add data cleanup |
+
+## Maintenance Notes
+
+### Recent Changes
+- [date] - Added mobile viewport tests
+- [date] - Refactored LoginPage selectors
+
+### Known Issues
+- Flaky on slow networks (timeout)
+- Mobile tests skip on CI
+
+### Improvement Opportunities
+1. Add visual regression tests
+2. Increase error case coverage
+3. Add API contract tests
+
+## Related Documentation
+
+- [Test Plan](../test-plans/login-test-plan.md)
+- [Feature Spec](../features/authentication.md)
+- [API Docs](../api/auth-endpoints.md)
+
+## Metadata
+
+| Property | Value |
+|----------|-------|
+| Analyzed | [timestamp] |
+| Framework | [framework] |
+| Test Files | [count] |
+| Page Objects | [count] |
+| Fixtures | [count] |
+```
+
+### Step 6: Resolve Open Questions
+
+Before completing, resolve any unclear areas:
+- Unclear test purposes
+- Missing documentation
+- Ambiguous dependencies
+
+Use AskUserQuestion for clarification.
+
+### Step 7: Summary
+
+```
+════════════════════════════════════════════════════════════════════
+                    📚 TEST KNOWLEDGE CAPTURED
+════════════════════════════════════════════════════════════════════
+
+📄 Documentation Created:
+   docs/test-knowledge-[name].md
+
+📊 Analysis Summary:
+   - Entry Point: [type] - [path]
+   - Test Files: [count]
+   - Page Objects: [count]
+   - Fixtures: [count]
+   - Test Cases: [count]
+
+🔍 Key Insights:
+   • [Insight 1 - e.g., "Well-structured POM hierarchy"]
+   • [Insight 2 - e.g., "Missing error case coverage"]
+   • [Insight 3 - e.g., "Good fixture organization"]
+
+⚠️ Issues Found:
+   • [Issue 1]
+   • [Issue 2]
+
+🔗 Suggested Next Captures:
+   • /qakit:docs/capture-test-knowledge [related-module-1]
+   • /qakit:docs/capture-test-knowledge [related-module-2]
+
+💡 Review the generated documentation for accuracy!
+════════════════════════════════════════════════════════════════════
+```
+
+## Use Cases
+
+### Onboarding New QA Engineers
+
+```bash
+# Document entire test architecture
+/qakit:docs/capture-test-knowledge tests/
+
+# Output: Complete test architecture overview
+```
+
+### Before Refactoring
+
+```bash
+# Understand current structure
+/qakit:docs/capture-test-knowledge pages/CheckoutPage.ts
+
+# Output: Page Object dependencies and usage
+```
+
+### Knowledge Transfer
+
+```bash
+# Document specific test flow
+/qakit:docs/capture-test-knowledge "payment processing flow"
+
+# Output: Flow diagram with all steps
+```
+
+### Test Review Preparation
+
+```bash
+# Analyze test module before review
+/qakit:docs/capture-test-knowledge tests/e2e/auth/
+
+# Output: Quality analysis and issues
+```
+
+$ARGUMENTS

package/templates/.claude/commands/qakit/docs/update-changelog.md

@@ -0,0 +1,207 @@
+# Update Test Changelog
+
+Update CHANGELOG.md with recent test-related changes following keepachangelog format.
+
+## Usage
+
+```
+/qakit:docs/update-changelog [--since=<date|commit>]
+```
+
+## Options
+
+| Option | Description |
+|--------|-------------|
+| `--since=<date>` | Changes since date (e.g., `2024-01-01`) |
+| `--since=<commit>` | Changes since commit (e.g., `HEAD~10`) |
+| (none) | Changes since last changelog entry |
+
+## Examples
+
+```bash
+/qakit:docs/update-changelog
+/qakit:docs/update-changelog --since=2024-01-15
+/qakit:docs/update-changelog --since=HEAD~20
+```
+
+## Instructions
+
+### Step 1: Find Last Changelog Entry
+
+```bash
+# Find last version/date in CHANGELOG.md
+grep -E "^## \[" CHANGELOG.md | head -1
+```
+
+If no CHANGELOG.md exists, create one.
+
+### Step 2: Gather Changes
+
+**Get git commits since last entry:**
+
+```bash
+# Get commits affecting test files
+git log --oneline --since="[date]" -- "*.spec.ts" "*.test.ts" "pages/" "fixtures/" | head -50
+
+# Get commits with test-related keywords
+git log --oneline --since="[date]" --grep="test" --grep="spec" --grep="fixture" --grep="page object" | head -30
+```
+
+**Scan for file changes:**
+
+```bash
+# New test files
+git diff --name-status [since]..HEAD | grep -E "^A.*\.(spec|test)\.(ts|js)$"
+
+# Modified test files
+git diff --name-status [since]..HEAD | grep -E "^M.*\.(spec|test)\.(ts|js)$"
+
+# New page objects
+git diff --name-status [since]..HEAD | grep -E "^A.*Page\.(ts|js)$"
+
+# New fixtures
+git diff --name-status [since]..HEAD | grep -E "^A.*(fixture|data)\.(ts|js)$"
+```
+
+### Step 3: Categorize Changes
+
+Group changes by category:
+
+**Added:**
+- New test files
+- New page objects
+- New fixtures
+- New test utilities
+- New test configurations
+
+**Changed:**
+- Updated test cases
+- Refactored page objects
+- Modified fixtures
+- Updated configurations
+
+**Fixed:**
+- Fixed flaky tests
+- Fixed broken selectors
+- Fixed test data issues
+
+**Removed:**
+- Deleted obsolete tests
+- Removed deprecated fixtures
+
+**Deprecated:**
+- Tests marked for removal
+- Old patterns being phased out
+
+### Step 4: Generate Changelog Entry
+
+```markdown
+## [Unreleased] - YYYY-MM-DD
+
+### Test Automation
+
+#### Added
+- New E2E tests for checkout flow (`checkout.spec.ts`)
+- LoginPage page object with authentication methods
+- Auth fixture with test user data
+- API helper for backend testing
+
+#### Changed
+- Refactored UserPage to use data-testid selectors
+- Updated test data fixtures for new user schema
+- Improved wait strategies in checkout tests
+
+#### Fixed
+- Fixed flaky login test (race condition in redirect)
+- Fixed broken selector in ProductPage
+- Fixed test data cleanup in afterEach hooks
+
+#### Removed
+- Removed deprecated legacy test utilities
+- Cleaned up unused fixtures
+
+### Test Coverage
+
+| Area | Before | After | Change |
+|------|--------|-------|--------|
+| Login | 85% | 92% | +7% |
+| Checkout | 70% | 88% | +18% |
+| User Profile | 60% | 75% | +15% |
+
+### Test Metrics
+
+- Total Tests: 145 (+12)
+- Pass Rate: 98.5% (+1.2%)
+- Flaky Tests: 2 (-3)
+- Avg Duration: 4m 32s (-45s)
+```
+
+### Step 5: Update CHANGELOG.md
+
+Insert new entry at the top of the changelog, after the header.
+
+**Changelog Header (if creating new):**
+
+```markdown
+# Test Automation Changelog
+
+All notable changes to test automation will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
+
+## [Unreleased]
+
+[New entries go here]
+
+---
+```
+
+### Step 6: Summary
+
+```
+════════════════════════════════════════════════════════════════════
+                    📝 CHANGELOG UPDATED
+════════════════════════════════════════════════════════════════════
+
+PERIOD: [start-date] to [end-date]
+
+CHANGES DOCUMENTED:
+  Added: [X] items
+  Changed: [Y] items
+  Fixed: [Z] items
+  Removed: [W] items
+
+FILES ANALYZED:
+  Commits: [count]
+  Test Files: [count]
+  Page Objects: [count]
+  Fixtures: [count]
+
+OUTPUT:
+  Updated: CHANGELOG.md
+
+💡 Review the changelog entry for accuracy before committing.
+════════════════════════════════════════════════════════════════════
+```
+
+## Changelog Categories for QA
+
+| Category | What to Include |
+|----------|-----------------|
+| **Added** | New tests, page objects, fixtures, utilities |
+| **Changed** | Refactored tests, updated selectors, modified data |
+| **Fixed** | Flaky tests, broken tests, selector fixes |
+| **Removed** | Deleted tests, removed deprecated code |
+| **Deprecated** | Tests marked for future removal |
+| **Security** | Security-related test updates |
+| **Performance** | Test performance improvements |
+
+## Best Practices
+
+1. **Be Specific**: Include file names and brief descriptions
+2. **Group Logically**: Keep related changes together
+3. **Include Metrics**: Add coverage/pass rate changes when significant
+4. **Link Issues**: Reference Jira tickets or GitHub issues
+5. **Date Entries**: Always include the date of changes
+
+$ARGUMENTS