ai-qakit 1.0.0

package/templates/.claude/commands/qakit/perf/script.md

@@ -0,0 +1,38 @@
+# Generate Performance Scripts
+
+Generate performance test scripts.
+
+## Usage
+```
+/qakit:perf/script [--tool k6|artillery|jmeter]
+```
+
+## Instructions
+
+Generate scripts for:
+- Load testing
+- Stress testing
+- Spike testing
+- Endurance testing
+
+## Output (k6)
+```javascript
+import http from 'k6/http';
+import { check, sleep } from 'k6';
+
+export const options = {
+  stages: [
+    { duration: '2m', target: 100 },
+    { duration: '5m', target: 100 },
+    { duration: '2m', target: 0 },
+  ],
+};
+
+export default function () {
+  const res = http.get('https://api.example.com/users');
+  check(res, { 'status is 200': (r) => r.status === 200 });
+  sleep(1);
+}
+```
+
+$ARGUMENTS

package/templates/.claude/commands/qakit/rca/analyze.md

@@ -0,0 +1,166 @@
+# Root Cause Analysis
+
+Perform Root Cause Analysis (RCA) for test failures following Enouvo QA standards.
+
+## Usage
+
+```
+/qakit:rca/analyze <test-failure-description>
+```
+
+## Purpose
+
+Determine why a test case failed and classify the issue accurately - whether it is a product defect, environment issue, or test setup error. This ensures accountability, learning, and prevention.
+
+## Instructions
+
+### Step 1: Classify the Failure
+
+| Category | Example Scenario | Owner |
+|----------|------------------|-------|
+| **Bug** | Actual defect in app logic, API, or UI | Development |
+| **Test Script Issue** | Automation failed due to incorrect locator or outdated steps | QA Automation |
+| **Data Issue** | Missing or invalid data (user, permission, references) | QA / DevOps |
+| **Environment Issue** | API downtime, build failure, or expired token | DevOps |
+| **Requirement Change** | Feature updated without test case adjustment | Product / QA |
+| **Flaky Test** | Inconsistent test failures due to async or timing issues | QA Automation |
+
+### Step 2: Investigate the Root Cause
+
+| Area to Check | How to Investigate |
+|---------------|-------------------|
+| **Logs and Evidence** | Review console logs, API responses, and screenshots of the failed test |
+| **Environment Stability** | Verify environment uptime, database connectivity, and deployment success |
+| **Build Version** | Confirm tests ran against the correct build or deployment tag |
+| **Requirement Match** | Cross-check with the latest Jira story or requirement changes |
+| **Automation Script** | Re-run manually. If manual passes but automation fails, script may be outdated |
+| **Data Setup** | Check test data creation jobs and preconditions for completeness |
+
+> **Tip**: Always reproduce the issue manually first to confirm whether it is a product issue or a test setup problem.
+
+### Step 3: Document the Root Cause
+
+Generate RCA report structure:
+
+```markdown
+# Root Cause Analysis Report
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| **Test Case ID** | [TC-XXX] |
+| **Test Case Title** | [Title] |
+| **Failure Date** | [Date] |
+| **Environment** | [Staging/Production] |
+| **Build Version** | [Version] |
+| **Analyzed By** | [Name] |
+
+## Failure Details
+
+### What Failed
+
+[Description of the test failure]
+
+### Error Message / Evidence
+
+```
+[Error message or screenshot description]
+```
+
+## Root Cause Analysis
+
+### Classification
+
+| Field | Value |
+|-------|-------|
+| **Root Cause Type** | Bug / Test Script Issue / Data Issue / Environment Issue / Requirement Change / Flaky Test |
+| **Owner** | [Development / QA / DevOps / Product] |
+
+### Investigation Steps
+
+1. [What was checked]
+2. [What was found]
+3. [Conclusion]
+
+### Root Cause Summary
+
+[Detailed explanation of why the failure occurred]
+
+## Resolution
+
+### Action Taken
+
+[Steps taken to resolve the issue]
+
+### Verification
+
+- [ ] Issue reproduced manually
+- [ ] Fix implemented
+- [ ] Re-tested and passed
+- [ ] Automation updated (if applicable)
+
+## Prevention
+
+### Preventive Actions
+
+| Root Cause | Preventive Action |
+|------------|-------------------|
+| [Cause] | [Action to prevent recurrence] |
+
+## Status
+
+| Field | Value |
+|-------|-------|
+| **Status** | Open / In Progress / Resolved / Closed |
+| **Resolution Date** | [Date] |
+| **Verified By** | [Name] |
+```
+
+### Step 4: Validate the Fix
+
+1. Reproduce the issue manually after fix implementation
+2. Re-run automation on the same environment
+3. Verify results in CI/CD pipeline
+4. Update the RCA report and mark as closed after validation passes
+
+### Step 5: Prevent Recurrence
+
+| Root Cause | Preventive Action |
+|------------|-------------------|
+| Requirement change not communicated | Include QA in sprint grooming or change review |
+| Data not refreshed | Automate test data setup before each smoke run |
+| Outdated script locators | Implement locator version tagging or element checks |
+| Flaky test timing | Add explicit waits or test retries in automation framework |
+| Environment instability | Add uptime monitoring and alerts |
+
+## Example RCA Summary
+
+| Test Case ID | RCA Summary | Root Cause Type | Resolution | Status |
+|--------------|-------------|-----------------|------------|--------|
+| WEB-LOGIN-001 | Cost Code dropdown incorrect due to new requirement AUTH-9963 | Requirement Change | Test case revised | Closed |
+| API-USER-015 | Event not displayed in Event Tab (Bug API-10249) | Bug | Fix by Dev, QA verified | Closed |
+| MOB-PAY-003 | Locator outdated in automation script | Test Script Issue | Locator updated | Closed |
+
+## Output Location
+
+Save RCA report to: `rca/[MODULE]/RCA-[TC-ID]-[DATE].md`
+
+## Best Practices
+
+### DO's ✅
+
+- Base conclusions on evidence, not assumptions
+- Check environment stability before re-running tests
+- Track recurring failures for systemic issues
+- Maintain consistent RCA format for easier reporting
+- Link test case IDs, Jira tickets, and CI job URLs for traceability
+
+### DON'Ts ❌
+
+- Don't assume the cause without investigation
+- Don't skip manual reproduction
+- Don't leave RCA incomplete
+- Don't ignore recurring patterns
+
+$ARGUMENTS

package/templates/.claude/commands/qakit/regression/analyze.md

@@ -0,0 +1,36 @@
+# Analyze Regression Impact
+
+Analyze code changes to determine regression testing needs.
+
+## Usage
+```
+/qakit:regression/analyze [--since commit|branch]
+```
+
+## Instructions
+
+1. **Analyze Changes**
+   - Identify modified files
+   - Map to test coverage
+   - Determine impact radius
+
+2. **Generate Impact Report**
+   ```markdown
+   # Regression Impact Analysis
+   
+   ## Changed Files
+   | File | Type | Impact |
+   |------|------|--------|
+   | auth/login.ts | Modified | High |
+   
+   ## Affected Tests
+   - Unit: 15 tests
+   - Integration: 8 tests
+   - E2E: 3 tests
+   
+   ## Recommended Regression Suite
+   - auth.test.ts
+   - login.e2e.ts
+   ```
+
+$ARGUMENTS

package/templates/.claude/commands/qakit/regression/report.md

@@ -0,0 +1,30 @@
+# Regression Test Report
+
+Generate regression test execution report.
+
+## Usage
+```
+/qakit:regression/report
+```
+
+## Output
+```markdown
+# Regression Test Report
+
+## Summary
+- Total: 45 tests
+- Passed: 43
+- Failed: 2
+- Duration: 28 minutes
+
+## Failed Tests
+| Test | Error | Impact |
+|------|-------|--------|
+| login.test | Timeout | High |
+
+## Recommendation
+- 2 failures need investigation
+- Safe to proceed with caution
+```
+
+$ARGUMENTS

package/templates/.claude/commands/qakit/regression/run.md

@@ -0,0 +1,17 @@
+# Run Regression Suite
+
+Execute selected regression tests.
+
+## Usage
+```
+/qakit:regression/run [--parallel] [--retry-failed]
+```
+
+## Instructions
+
+1. Run selected regression tests
+2. Track execution progress
+3. Retry failed tests if configured
+4. Generate execution log
+
+$ARGUMENTS

package/templates/.claude/commands/qakit/regression/select.md

@@ -0,0 +1,34 @@
+# Select Regression Tests
+
+Select optimal regression test suite based on changes.
+
+## Usage
+```
+/qakit:regression/select [--risk-based] [--time-budget minutes]
+```
+
+## Instructions
+
+Select tests using:
+- Change impact analysis
+- Risk-based prioritization
+- Time budget constraints
+- Historical failure data
+
+## Output
+```markdown
+# Selected Regression Tests
+
+## Selection Criteria
+- Time budget: 30 minutes
+- Risk level: High priority first
+
+## Selected Tests (45 tests)
+| Suite | Tests | Est. Time |
+|-------|-------|-----------|
+| auth | 15 | 5 min |
+| api | 20 | 15 min |
+| e2e | 10 | 10 min |
+```
+
+$ARGUMENTS

package/templates/.claude/commands/qakit/research/deep.md

@@ -0,0 +1,328 @@
+# Deep Research - Testing Tools & Practices
+
+Deep research on testing tools, frameworks, and best practices with comprehensive report generation.
+
+## Usage
+
+```
+/qakit:research/deep [topic | technology | question]
+```
+
+## Examples
+
+```bash
+/qakit:research/deep "Playwright vs Cypress comparison 2024"
+/qakit:research/deep "Mobile testing with Appium best practices"
+/qakit:research/deep "How to implement visual regression testing"
+/qakit:research/deep "API contract testing with Pact"
+/qakit:research/deep "Performance testing with k6"
+```
+
+## Instructions
+
+### Step 1: Classify Research Topic
+
+Identify research category:
+
+| Category | Indicators | Focus |
+|----------|------------|-------|
+| Framework Comparison | "vs", "compare", "which" | Pros/cons, use cases |
+| Best Practices | "best practices", "how to" | Patterns, guidelines |
+| Tool Deep Dive | Specific tool name | Features, setup, usage |
+| Problem Solving | "how to fix", "issue with" | Solutions, workarounds |
+| Trends | "2024", "latest", "new" | Current state, future |
+
+### Step 2: Define Search Strategy
+
+Create up to 5 focused search queries:
+
+**For Framework Comparison:**
+1. "[Framework A] vs [Framework B] 2024"
+2. "[Framework A] pros cons"
+3. "[Framework B] pros cons"
+4. "when to use [Framework A]"
+5. "[Framework A] [Framework B] performance benchmark"
+
+**For Best Practices:**
+1. "[Topic] best practices 2024"
+2. "[Topic] patterns"
+3. "[Topic] common mistakes"
+4. "[Topic] examples"
+5. "[Topic] guide"
+
+**For Tool Deep Dive:**
+1. "[Tool] documentation"
+2. "[Tool] getting started"
+3. "[Tool] advanced features"
+4. "[Tool] integration"
+5. "[Tool] troubleshooting"
+
+### Step 3: Execute Research
+
+**Search for information:**
+
+Use web search to gather information from:
+- Official documentation
+- GitHub repositories
+- Tech blogs (Medium, Dev.to)
+- Stack Overflow
+- Conference talks/videos
+
+**Evaluate sources:**
+
+| Criteria | Weight |
+|----------|--------|
+| Authority (official docs, maintainers) | High |
+| Recency (< 1 year old) | High |
+| Quality (detailed, examples) | Medium |
+| Community validation (stars, upvotes) | Medium |
+
+### Step 4: Extract Key Information
+
+For each source, extract:
+- Key findings
+- Code examples
+- Configuration snippets
+- Pros and cons
+- Use cases
+- Limitations
+
+### Step 5: Cross-Validate
+
+- Compare information across sources
+- Identify consensus vs conflicting views
+- Note areas of uncertainty
+- Verify with official documentation
+
+### Step 6: Generate Research Report
+
+Create comprehensive report:
+
+```markdown
+# Research Report: [Topic]
+
+> Generated: [date]
+> Research Depth: Deep
+> Sources Analyzed: [count]
+
+## Executive Summary
+
+[2-3 paragraph summary of key findings]
+
+## Key Findings
+
+### Finding 1: [Title]
+
+[Detailed explanation with evidence]
+
+**Source:** [link]
+
+### Finding 2: [Title]
+
+[Detailed explanation with evidence]
+
+**Source:** [link]
+
+## Comparison Table (if applicable)
+
+| Aspect | Option A | Option B |
+|--------|----------|----------|
+| Learning Curve | Easy | Moderate |
+| Performance | Fast | Very Fast |
+| Community | Large | Growing |
+| Documentation | Excellent | Good |
+| Mobile Support | Limited | Full |
+
+## Best Practices
+
+### Do's ✅
+
+1. **[Practice 1]**
+   - Explanation
+   - Example
+
+2. **[Practice 2]**
+   - Explanation
+   - Example
+
+### Don'ts ❌
+
+1. **[Anti-pattern 1]**
+   - Why it's bad
+   - Alternative
+
+2. **[Anti-pattern 2]**
+   - Why it's bad
+   - Alternative
+
+## Implementation Guide
+
+### Prerequisites
+
+- [Requirement 1]
+- [Requirement 2]
+
+### Step-by-Step Setup
+
+1. **Install dependencies**
+   ```bash
+   npm install [package]
+   ```
+
+2. **Configure**
+   ```typescript
+   // config.ts
+   export default {
+     // configuration
+   };
+   ```
+
+3. **Create first test**
+   ```typescript
+   // example.spec.ts
+   test('example', async () => {
+     // test code
+   });
+   ```
+
+## Code Examples
+
+### Example 1: [Use Case]
+
+```typescript
+// Detailed code example with comments
+```
+
+### Example 2: [Use Case]
+
+```typescript
+// Another example
+```
+
+## Security Considerations
+
+- [Security point 1]
+- [Security point 2]
+
+## Performance Considerations
+
+- [Performance point 1]
+- [Performance point 2]
+
+## Common Pitfalls
+
+| Pitfall | Impact | Solution |
+|---------|--------|----------|
+| [Pitfall 1] | High | [Solution] |
+| [Pitfall 2] | Medium | [Solution] |
+
+## Recommendations
+
+### For Small Projects
+- [Recommendation]
+
+### For Large Projects
+- [Recommendation]
+
+### For Enterprise
+- [Recommendation]
+
+## Resources
+
+### Official Documentation
+- [Link 1]
+- [Link 2]
+
+### Tutorials
+- [Link 1]
+- [Link 2]
+
+### Community
+- [Link 1]
+- [Link 2]
+
+## Conclusion
+
+[Summary of recommendations and next steps]
+
+---
+
+## Research Metadata
+
+| Property | Value |
+|----------|-------|
+| Topic | [topic] |
+| Date | [date] |
+| Sources | [count] |
+| Confidence | High/Medium/Low |
+```
+
+### Step 7: Summary
+
+```
+════════════════════════════════════════════════════════════════════
+                    🔬 RESEARCH COMPLETE
+════════════════════════════════════════════════════════════════════
+
+TOPIC: [Research Topic]
+
+📊 RESEARCH SUMMARY:
+  Sources Analyzed: [count]
+  Key Findings: [count]
+  Code Examples: [count]
+  Recommendations: [count]
+
+📄 REPORT GENERATED:
+  docs/research/[topic-slug].md
+
+💡 KEY TAKEAWAYS:
+  1. [Takeaway 1]
+  2. [Takeaway 2]
+  3. [Takeaway 3]
+
+🎯 RECOMMENDED NEXT STEPS:
+  1. [Action 1]
+  2. [Action 2]
+
+════════════════════════════════════════════════════════════════════
+```
+
+## Research Topics for QA
+
+### Framework Research
+- Playwright vs Cypress vs WebdriverIO
+- Jest vs Vitest vs Mocha
+- Appium vs Detox for mobile
+- k6 vs Artillery vs Gatling
+
+### Practice Research
+- Page Object Model patterns
+- Test data management strategies
+- CI/CD integration best practices
+- Visual regression testing approaches
+- API contract testing methods
+
+### Tool Research
+- Playwright advanced features
+- Allure reporting setup
+- BrowserStack/Sauce Labs integration
+- Test management tools (TestRail, Testmo)
+
+### Problem Research
+- Handling flaky tests
+- Reducing test execution time
+- Cross-browser testing strategies
+- Mobile testing challenges
+
+## Output
+
+Research report saved to `docs/research/[topic-slug].md` with:
+- Executive summary
+- Detailed findings with sources
+- Comparison tables
+- Code examples
+- Best practices
+- Implementation guide
+- Resources and references
+
+$ARGUMENTS