ai-qakit 1.0.0

package/templates/.claude/commands/qakit/jira/create-tests.md

@@ -0,0 +1,319 @@
+# Create Tests from Jira Ticket
+
+Generate comprehensive test cases from Jira ticket analysis including subtasks, linked issues, and comments.
+
+## Usage
+
+```
+/qakit:jira/create-tests PROJ-123
+/qakit:jira/create-tests PROJ-123 --format=playwright
+/qakit:jira/create-tests PROJ-123 --format=jest
+/qakit:jira/create-tests PROJ-123 --output=tests/auth/
+```
+
+## Prerequisites
+
+Set environment variables:
+```bash
+export JIRA_BASE_URL="https://yourcompany.atlassian.net"
+export JIRA_EMAIL="your.email@company.com"
+export JIRA_API_TOKEN="your-api-token"
+```
+
+## Instructions
+
+### Step 1: Run Analysis First
+
+Internally call `/qakit:jira/analyze` logic to gather:
+- Main ticket details
+- Subtasks
+- Linked issues
+- Comments with test hints
+- Acceptance criteria
+
+### Step 2: Categorize Test Requirements
+
+Group requirements by test type:
+
+| Source | Test Type |
+|--------|-----------|
+| Acceptance Criteria | Functional tests |
+| Subtasks | Unit/Component tests |
+| Linked issues | Integration tests |
+| Comments (edge cases) | Edge case tests |
+| Security labels | Security tests |
+| Performance labels | Performance tests |
+
+### Step 3: Generate Test Cases Document
+
+Create `docs/test-cases/{TICKET_ID}-tests.md`:
+
+```markdown
+# Test Cases: {TICKET_ID}
+
+## Overview
+
+| Field | Value |
+|-------|-------|
+| **Jira Ticket** | [PROJ-123](link) |
+| **Feature** | User Authentication |
+| **Generated** | 2024-01-20 |
+| **Total Tests** | 15 |
+
+## Test Cases
+
+### TC-001: Valid Login
+
+| Field | Value |
+|-------|-------|
+| **ID** | TC-001 |
+| **Title** | Valid login with email and password |
+| **Priority** | P0 |
+| **Type** | Functional |
+| **Source** | AC-001 |
+| **Automated** | ✅ |
+
+**Preconditions:**
+- User account exists
+- User is on login page
+
+**Test Steps:**
+1. Enter valid email
+2. Enter valid password
+3. Click login button
+
+**Expected Result:**
+- User is redirected to dashboard
+- Session is created
+- Welcome message displayed
+
+**Test Data:**
+| Email | Password | Expected |
+|-------|----------|----------|
+| user@test.com | ValidPass123! | Success |
+
+---
+
+### TC-002: Invalid Email Format
+
+| Field | Value |
+|-------|-------|
+| **ID** | TC-002 |
+| **Title** | Validation error for invalid email format |
+| **Priority** | P1 |
+| **Type** | Validation |
+| **Source** | AC-002 |
+
+**Test Steps:**
+1. Enter invalid email format
+2. Click login button
+
+**Expected Result:**
+- Error message: "Please enter a valid email"
+- Form not submitted
+
+**Test Data:**
+| Email | Expected Error |
+|-------|----------------|
+| invalid | Invalid email format |
+| @test.com | Invalid email format |
+| user@ | Invalid email format |
+| user@.com | Invalid email format |
+
+---
+```
+
+### Step 4: Generate Test Code (Optional)
+
+If `--format` specified, generate executable tests:
+
+#### Playwright Format
+```typescript
+// tests/auth/login.spec.ts
+import { test, expect } from '@playwright/test';
+
+/**
+ * Test Suite: User Authentication
+ * Jira: PROJ-123
+ * Generated: 2024-01-20
+ */
+
+test.describe('Login Feature @PROJ-123', () => {
+  
+  test.beforeEach(async ({ page }) => {
+    await page.goto('/login');
+  });
+
+  /**
+   * TC-001: Valid login with email and password
+   * Source: AC-001
+   * Priority: P0
+   */
+  test('TC-001: should login successfully with valid credentials', async ({ page }) => {
+    // Arrange
+    const email = 'user@test.com';
+    const password = 'ValidPass123!';
+    
+    // Act
+    await page.fill('[data-testid="email"]', email);
+    await page.fill('[data-testid="password"]', password);
+    await page.click('[data-testid="login-button"]');
+    
+    // Assert
+    await expect(page).toHaveURL('/dashboard');
+    await expect(page.locator('[data-testid="welcome-message"]')).toBeVisible();
+  });
+
+  /**
+   * TC-002: Validation error for invalid email format
+   * Source: AC-002
+   * Priority: P1
+   */
+  test('TC-002: should show error for invalid email format', async ({ page }) => {
+    // Test data from Jira
+    const invalidEmails = ['invalid', '@test.com', 'user@', 'user@.com'];
+    
+    for (const email of invalidEmails) {
+      await page.fill('[data-testid="email"]', email);
+      await page.click('[data-testid="login-button"]');
+      await expect(page.locator('[data-testid="email-error"]')).toContainText('valid email');
+    }
+  });
+
+  /**
+   * TC-003: Account lockout after failed attempts
+   * Source: AC-003
+   * Priority: P0
+   */
+  test('TC-003: should lock account after 5 failed attempts', async ({ page }) => {
+    const email = 'user@test.com';
+    const wrongPassword = 'WrongPass!';
+    
+    // Attempt 5 failed logins
+    for (let i = 0; i < 5; i++) {
+      await page.fill('[data-testid="email"]', email);
+      await page.fill('[data-testid="password"]', wrongPassword);
+      await page.click('[data-testid="login-button"]');
+    }
+    
+    // Assert account locked
+    await expect(page.locator('[data-testid="error-message"]'))
+      .toContainText('Account locked');
+  });
+
+  /**
+   * TC-004: Special characters in password
+   * Source: Comment by QA Lead
+   * Priority: P1
+   */
+  test('TC-004: should handle special characters in password', async ({ page }) => {
+    const testCases = [
+      { password: 'Pass@123!', expected: 'success' },
+      { password: 'Pass#$%^&*', expected: 'success' },
+      { password: "Pass'quote", expected: 'success' },
+      { password: 'Pass"double', expected: 'success' },
+    ];
+    
+    for (const tc of testCases) {
+      // Test each special character case
+    }
+  });
+});
+```
+
+#### Jest Format
+```typescript
+// tests/auth/login.test.ts
+import { login, validateEmail } from '../src/auth';
+
+/**
+ * Test Suite: User Authentication
+ * Jira: PROJ-123
+ */
+
+describe('Login Feature @PROJ-123', () => {
+  
+  describe('Email Validation', () => {
+    /**
+     * TC-002: Invalid email format
+     * Source: AC-002
+     */
+    test.each([
+      ['invalid', false],
+      ['@test.com', false],
+      ['user@', false],
+      ['user@test.com', true],
+    ])('validateEmail(%s) should return %s', (email, expected) => {
+      expect(validateEmail(email)).toBe(expected);
+    });
+  });
+
+  describe('Login Function', () => {
+    /**
+     * TC-001: Valid login
+     * Source: AC-001
+     */
+    test('should return user on valid credentials', async () => {
+      const result = await login('user@test.com', 'ValidPass123!');
+      expect(result.success).toBe(true);
+      expect(result.user).toBeDefined();
+    });
+  });
+});
+```
+
+### Step 5: Create Test Data File (Optional)
+
+```typescript
+// tests/fixtures/auth-test-data.ts
+export const loginTestData = {
+  validUsers: [
+    { email: 'user@test.com', password: 'ValidPass123!' },
+    { email: 'admin@test.com', password: 'AdminPass456!' },
+  ],
+  invalidEmails: [
+    'invalid',
+    '@test.com', 
+    'user@',
+    'user@.com',
+  ],
+  specialCharPasswords: [
+    'Pass@123!',
+    'Pass#$%^&*',
+    "Pass'quote",
+  ],
+};
+```
+
+## Output Files
+
+| File | Description |
+|------|-------------|
+| `docs/test-cases/{TICKET}-tests.md` | Test case documentation |
+| `tests/{feature}/{ticket}.spec.ts` | Playwright tests (if --format=playwright) |
+| `tests/{feature}/{ticket}.test.ts` | Jest tests (if --format=jest) |
+| `tests/fixtures/{ticket}-data.ts` | Test data fixtures |
+
+## Traceability
+
+Each generated test includes:
+- Jira ticket reference in describe/test name
+- Source acceptance criteria ID
+- Priority level
+- Link back to original requirement
+
+## Next Steps
+
+After generating tests:
+
+1. Review and customize generated tests
+2. Add to test suite:
+   ```
+   /qakit:test/create-test-suite --add tests/auth/
+   ```
+3. Run tests:
+   ```
+   npm test -- --grep="@PROJ-123"
+   ```
+
+$ARGUMENTS

package/templates/.claude/commands/qakit/kb/add-design.md

@@ -0,0 +1,258 @@
+# Add Design to Knowledge Base
+
+Add design assets (screenshots, Figma links, mockups) to a feature in the knowledge base.
+
+## Usage
+
+```
+/qakit:kb/add-design --feature=maps-resource-toggle
+/qakit:kb/add-design --feature=maps-resource-toggle --figma=https://figma.com/...
+/qakit:kb/add-design docs/features/maps-resource-toggle.md
+```
+
+## Instructions
+
+### Step 1: Identify Target Feature
+
+```bash
+# If --feature provided
+FEATURE_FILE="docs/features/${FEATURE_NAME}.md"
+
+# If file path provided
+FEATURE_FILE="$INPUT"
+
+# Validate exists
+if [ ! -f "$FEATURE_FILE" ]; then
+  echo "Feature not found: $FEATURE_FILE"
+  echo "Available features:"
+  ls docs/features/*.md
+  exit 1
+fi
+```
+
+### Step 2: Determine Design Type
+
+**Options:**
+1. **Screenshot/Image** - User will paste or drag image
+2. **Figma link** - Provide Figma URL
+3. **Local file** - Path to existing image
+
+### Step 3: For Image/Screenshot
+
+**Prompt user:**
+```
+Please provide the design:
+1. Paste/drag an image here
+2. Or provide a file path
+3. Or provide a Figma URL with --figma=URL
+
+Describe what this design shows:
+> [User input: "Resource panel open state with 3 items"]
+```
+
+**Save image:**
+```bash
+# Generate filename
+DESIGN_ID="${FEATURE_NAME}-$(date +%Y%m%d-%H%M%S)"
+DESIGN_PATH="docs/assets/screenshots/${DESIGN_ID}.png"
+
+# Save image to path
+# (Claude Code handles image saving)
+
+echo "Saved: $DESIGN_PATH"
+```
+
+### Step 4: Analyze Design (if AI vision available)
+
+**Extract from image:**
+- UI components visible
+- States shown (open/closed, loading, error)
+- Interactive elements (buttons, inputs)
+- Data displayed
+- Layout structure
+
+**Generate analysis:**
+```markdown
+### Design Analysis: {DESIGN_ID}
+
+**UI Elements Identified:**
+- Resource panel (right sidebar)
+- Resource list (3 items)
+- Close button (X, top-right)
+- Filter dropdown (top)
+- Search input (below filter)
+
+**States Shown:**
+- Panel: Open
+- List: Populated (3 items)
+- Loading: No
+
+**Interactive Elements:**
+- Close button → Closes panel
+- Filter dropdown → Filters resources
+- Resource item → Opens detail view
+
+**Suggested Test Points:**
+- Verify panel opens correctly
+- Verify 3 resources displayed
+- Verify close button works
+- Verify filter functionality
+```
+
+### Step 5: For Figma Link
+
+```bash
+FIGMA_URL="$FIGMA_PARAM"
+
+# Extract Figma file/frame info
+# Format: https://figma.com/file/{file_id}/{file_name}?node-id={node_id}
+
+# Store reference (don't download)
+```
+
+**Generate reference:**
+```markdown
+### Figma Design: {title}
+
+**URL:** {FIGMA_URL}
+**Added:** {timestamp}
+
+**Notes:**
+{User-provided description}
+
+**Frames/Screens:**
+- Main view
+- Loading state
+- Error state
+- Empty state
+```
+
+### Step 6: Update Feature Document
+
+**Add to feature doc frontmatter:**
+```yaml
+sources:
+  - type: jira
+    id: "LG-4018"
+    ...
+  - type: design
+    id: "{DESIGN_ID}"
+    path: "assets/screenshots/{DESIGN_ID}.png"
+    description: "Resource panel open state"
+    captured: "{timestamp}"
+```
+
+**Add Designs section to feature doc:**
+```markdown
+## Designs
+
+### {DESIGN_ID}: {Description}
+
+![{Description}](../assets/screenshots/{DESIGN_ID}.png)
+
+**Added:** {timestamp}
+**Source:** Screenshot / Figma
+
+**UI Elements:**
+- Resource panel (right sidebar)
+- Resource list with items
+- Close button
+- Filter controls
+
+**States Shown:**
+- Open state with data
+
+**Test Points from Design:**
+| ID | Test Point | Priority |
+|----|------------|----------|
+| DP-001 | Panel displays correctly | P0 |
+| DP-002 | Close button visible and clickable | P0 |
+| DP-003 | Resource items render correctly | P1 |
+| DP-004 | Filter dropdown functional | P1 |
+```
+
+### Step 7: Update Sources Registry
+
+**Update docs/_sources.json:**
+```json
+{
+  "sources": [
+    ...,
+    {
+      "id": "{DESIGN_ID}",
+      "type": "design",
+      "path": "docs/assets/screenshots/{DESIGN_ID}.png",
+      "description": "{description}",
+      "captured": "{timestamp}",
+      "linkedDocs": ["docs/features/{feature-name}.md"],
+      "extractedTestPoints": ["DP-001", "DP-002", "DP-003"]
+    }
+  ]
+}
+```
+
+### Step 8: Output Summary
+
+```markdown
+✅ Design Added to Knowledge Base
+
+## Design
+- **ID:** {DESIGN_ID}
+- **Type:** Screenshot
+- **Path:** docs/assets/screenshots/{DESIGN_ID}.png
+
+## Linked To
+- docs/features/{feature-name}.md
+
+## Analysis
+- **UI Elements:** 5 identified
+- **States:** 1 shown
+- **Test Points:** 4 suggested
+
+## Updated Files
+- docs/features/{feature-name}.md (added Designs section)
+- docs/_sources.json (added source entry)
+
+## Next Steps
+
+1. Add more designs:
+   /qakit:kb/add-design --feature={feature-name}
+
+2. Add different states:
+   - Loading state
+   - Error state
+   - Empty state
+
+3. Link to Figma:
+   /qakit:kb/add-design --feature={feature-name} --figma=URL
+```
+
+## Multiple States Workflow
+
+For comprehensive design coverage, add multiple states:
+
+```bash
+# Open state
+/qakit:kb/add-design --feature=resource-panel --state=open
+
+# Loading state
+/qakit:kb/add-design --feature=resource-panel --state=loading
+
+# Error state
+/qakit:kb/add-design --feature=resource-panel --state=error
+
+# Empty state
+/qakit:kb/add-design --feature=resource-panel --state=empty
+```
+
+## Options
+
+| Option | Description | Default |
+|--------|-------------|---------|
+| `--feature=NAME` | Target feature | Required |
+| `--figma=URL` | Figma design URL | - |
+| `--state=STATE` | UI state name | - |
+| `--description=TEXT` | Design description | - |
+| `--no-analysis` | Skip AI analysis | false |
+
+$ARGUMENTS