# BMAD Test Suite

Comprehensive test coverage for the BMAD framework including schema validation and module unit tests.

## Overview

This test suite includes:
- **Agent Schema Validation** - Validates `*.agent.yaml` files conform to specification
- **Crowdsource Library Tests** - FeedbackManager, SynthesisEngine, SignoffManager
- **Notification Service Tests** - Multi-channel notifications (GitHub, Slack, Email)
- **Cache Manager Tests** - PRD/Epic extensions for crowdsourcing

## Quick Start

```bash
# Run all tests
npm test

# Run with coverage report
npm run test:coverage

# Run specific test suites
npx vitest run test/unit/crowdsource/
npx vitest run test/unit/notifications/
npx vitest run test/unit/cache/
```

---

# Agent Schema Validation

Validates the Zod-based schema validator (`tools/schema/agent.js`) that ensures all `*.agent.yaml` files conform to the BMAD agent specification.

## Test Statistics

- **Total Test Fixtures**: 50
- **Valid Test Cases**: 18
- **Invalid Test Cases**: 32
- **Code Coverage**: 100% all metrics (statements, branches, functions, lines)
- **Exit Code Tests**: 4 CLI integration tests

## Quick Start

```bash
# Run all tests
npm test

# Run with coverage report
npm run test:coverage

# Run CLI integration tests
./test/test-cli-integration.sh

# Validate actual agent files
npm run validate:schemas
```

## Test Organization

### Test Fixtures

Located in `test/fixtures/agent-schema/`, organized by category:

```
test/fixtures/agent-schema/
├── valid/                    # 15 fixtures that should pass
│   ├── top-level/           # Basic structure tests
│   ├── metadata/            # Metadata field tests
│   ├── persona/             # Persona field tests
│   ├── critical-actions/    # Critical actions tests
│   ├── menu/                # Menu structure tests
│   ├── menu-commands/       # Command target tests
│   ├── menu-triggers/       # Trigger format tests
│   └── prompts/             # Prompts field tests
└── invalid/                  # 32 fixtures that should fail
    ├── top-level/           # Structure errors
    ├── metadata/            # Metadata validation errors
    ├── persona/             # Persona validation errors
    ├── critical-actions/    # Critical actions errors
    ├── menu/                # Menu errors
    ├── menu-commands/       # Command target errors
    ├── menu-triggers/       # Trigger format errors
    ├── prompts/             # Prompts errors
    └── yaml-errors/         # YAML parsing errors
```

## Test Categories

### 1. Top-Level Structure Tests (4 fixtures)

Tests the root-level agent structure:

- ✅ Valid: Minimal core agent with required fields
- ❌ Invalid: Empty YAML file
- ❌ Invalid: Missing `agent` key
- ❌ Invalid: Extra top-level keys (strict mode)

### 2. Metadata Field Tests (7 fixtures)

Tests agent metadata validation:

- ✅ Valid: Module agent with correct `module` field
- ❌ Invalid: Missing required fields (`id`, `name`, `title`, `icon`)
- ❌ Invalid: Empty strings in metadata
- ❌ Invalid: Module agent missing `module` field
- ❌ Invalid: Core agent with unexpected `module` field
- ❌ Invalid: Wrong `module` value (doesn't match path)
- ❌ Invalid: Extra unknown metadata fields

### 3. Persona Field Tests (6 fixtures)

Tests persona structure and validation:

- ✅ Valid: Complete persona with all fields
- ❌ Invalid: Missing required fields (`role`, `identity`, etc.)
- ❌ Invalid: `principles` as string instead of array
- ❌ Invalid: Empty `principles` array
- ❌ Invalid: Empty strings in `principles` array
- ❌ Invalid: Extra unknown persona fields

### 4. Critical Actions Tests (5 fixtures)

Tests optional `critical_actions` field:

- ✅ Valid: No `critical_actions` field (optional)
- ✅ Valid: Empty `critical_actions` array
- ✅ Valid: Valid action strings
- ❌ Invalid: Empty strings in actions
- ❌ Invalid: Actions as non-array type

### 5. Menu Field Tests (4 fixtures)

Tests required menu structure:

- ✅ Valid: Single menu item
- ✅ Valid: Multiple menu items with different commands
- ❌ Invalid: Missing `menu` field
- ❌ Invalid: Empty `menu` array

### 6. Menu Command Target Tests (4 fixtures)

Tests menu item command targets:

- ✅ Valid: All 6 command types (`workflow`, `validate-workflow`, `exec`, `action`, `tmpl`, `data`)
- ✅ Valid: Multiple command targets in one menu item
- ❌ Invalid: No command target fields
- ❌ Invalid: Empty string command targets

### 7. Menu Trigger Validation Tests (7 fixtures)

Tests trigger format enforcement:

- ✅ Valid: Kebab-case triggers (`help`, `list-tasks`, `multi-word-trigger`)
- ❌ Invalid: Leading asterisk (`*help`)
- ❌ Invalid: CamelCase (`listTasks`)
- ❌ Invalid: Snake_case (`list_tasks`)
- ❌ Invalid: Spaces (`list tasks`)
- ❌ Invalid: Duplicate triggers within agent
- ❌ Invalid: Empty trigger string

### 8. Prompts Field Tests (8 fixtures)

Tests optional `prompts` field:

- ✅ Valid: No `prompts` field (optional)
- ✅ Valid: Empty `prompts` array
- ✅ Valid: Prompts with required `id` and `content`
- ✅ Valid: Prompts with optional `description`
- ❌ Invalid: Missing `id`
- ❌ Invalid: Missing `content`
- ❌ Invalid: Empty `content` string
- ❌ Invalid: Extra unknown prompt fields

### 9. YAML Parsing Tests (2 fixtures)

Tests YAML parsing error handling:

- ❌ Invalid: Malformed YAML syntax
- ❌ Invalid: Invalid indentation

## Test Scripts

### Main Test Runner

**File**: `test/test-agent-schema.js`

Automated test runner that:

- Loads all fixtures from `test/fixtures/agent-schema/`
- Validates each against the schema
- Compares results with expected outcomes (parsed from YAML comments)
- Reports detailed results by category
- Exits with code 0 (pass) or 1 (fail)

**Usage**:

```bash
npm test
# or
node test/test-agent-schema.js
```

### Coverage Report

**Command**: `npm run test:coverage`

Generates code coverage report using c8:

- Text output to console
- HTML report in `coverage/` directory
- Tracks statement, branch, function, and line coverage

**Current Coverage**:

- Statements: 100%
- Branches: 100%
- Functions: 100%
- Lines: 100%

### CLI Integration Tests

**File**: `test/test-cli-integration.sh`

Bash script that tests CLI behavior:

1. Validates existing agent files
2. Verifies test fixture validation
3. Checks exit code 0 for valid files
4. Verifies test runner output format

**Usage**:

```bash
./test/test-cli-integration.sh
```

## Manual Testing

See **[MANUAL-TESTING.md](./MANUAL-TESTING.md)** for detailed manual testing procedures, including:

- Testing with invalid files
- GitHub Actions workflow verification
- Troubleshooting guide
- PR merge blocking tests

## Coverage Achievement

**100% code coverage achieved!** All branches, statements, functions, and lines in the validation logic are tested.

Edge cases covered include:

- Malformed module paths (e.g., `src/modules/bmm` without `/agents/`)
- Empty module names in paths (e.g., `src/modules//agents/`)
- Whitespace-only module field values
- All validation error paths
- All success paths for valid configurations

## Adding New Tests

To add new test cases:

1. Create a new `.agent.yaml` file in the appropriate `valid/` or `invalid/` subdirectory
2. Add comment metadata at the top:

   ```yaml
   # Test: Description of what this tests
   # Expected: PASS (or FAIL - error description)
   # Path context: src/modules/bmm/agents/test.agent.yaml (if needed)
   ```

3. Run the test suite to verify: `npm test`

## Integration with CI/CD

The validation is integrated into the GitHub Actions workflow:

**File**: `.github/workflows/lint.yaml`

**Job**: `agent-schema`

**Runs on**: All pull requests

**Blocks merge if**: Validation fails

## Files

- `test/test-agent-schema.js` - Main test runner
- `test/test-cli-integration.sh` - CLI integration tests
- `test/MANUAL-TESTING.md` - Manual testing guide
- `test/fixtures/agent-schema/` - Test fixtures (47 files)
- `tools/schema/agent.js` - Validation logic (under test)
- `tools/validate-agent-schema.js` - CLI wrapper

## Dependencies

- **zod**: Schema validation library
- **yaml**: YAML parsing
- **glob**: File pattern matching
- **c8**: Code coverage reporting

## Success Criteria

All success criteria from the original task have been exceeded:

- ✅ 50 test fixtures covering all validation rules (target: 47+)
- ✅ Automated test runner with detailed reporting
- ✅ CLI integration tests verifying exit codes and output
- ✅ Manual testing documentation
- ✅ **100% code coverage achieved** (target: 99%+)
- ✅ Both positive and negative test cases
- ✅ Clear and actionable error messages
- ✅ GitHub Actions integration verified
- ✅ Aggressive defensive assertions implemented

## Resources

- **Schema Documentation**: `schema-classification.md`
- **Validator Implementation**: `tools/schema/agent.js`
- **CLI Tool**: `tools/validate-agent-schema.js`
- **Project Guidelines**: `CLAUDE.md`

---

# Module Unit Tests

Unit tests for BMAD library modules using Vitest.

## Test Organization

```
test/unit/
├── crowdsource/                    # PRD/Epic crowdsourcing
│   ├── feedback-manager.test.js    # Feedback creation, querying, conflict detection
│   ├── synthesis-engine.test.js    # LLM synthesis, theme extraction
│   └── signoff-manager.test.js     # Sign-off thresholds, approval tracking
├── notifications/                   # Multi-channel notifications
│   ├── github-notifier.test.js     # GitHub @mentions, issue comments
│   ├── slack-notifier.test.js      # Slack webhook integration
│   ├── email-notifier.test.js      # SMTP, SendGrid, SES providers
│   └── notification-service.test.js # Orchestration, retry logic
├── cache/                           # Cache management
│   └── cache-manager-prd-epic.test.js # PRD/Epic extensions
├── config/                          # Configuration tests
├── core/                            # Core functionality
├── file-ops/                        # File operations
├── transformations/                 # Data transformations
└── utils/                           # Utility functions
```

## Crowdsource Tests

Tests for async stakeholder collaboration on PRDs and Epics:

### FeedbackManager
- Feedback types and status constants
- Creating feedback issues with proper labels
- Querying feedback by section/type/status
- Conflict detection between stakeholders
- Statistics aggregation

### SynthesisEngine
- LLM prompt templates for PRD/Epic synthesis
- Theme and keyword extraction
- Conflict identification and resolution
- Story split prompts for epics

### SignoffManager
- Three threshold types: count, percentage, required_approvers
- Approval progress tracking
- Blocking behavior
- Deadline management

## Notification Tests

Tests for multi-channel notification delivery:

### Notifiers
- **GitHub**: Template rendering, issue comments, @mentions
- **Slack**: Webhook payloads, Block Kit templates, dynamic colors
- **Email**: HTML/text templates, provider abstraction

### NotificationService
- Channel orchestration (send to GitHub + Slack + Email)
- Priority-based behavior (urgent = retry on failure)
- Convenience methods for all event types
- Graceful degradation when channels disabled

## Cache Tests

Tests for PRD/Epic extensions to cache-manager:

- Read/write PRD and Epic documents
- Metadata migration (v1 → v2)
- Status filtering and updates
- User task queries (`getMyTasks`, `getPrdsNeedingAttention`)
- Extended statistics with PRD/Epic counts
- Atomic file operations

## Running Unit Tests

```bash
# All unit tests
npx vitest run test/unit/

# With watch mode
npx vitest test/unit/

# Specific module
npx vitest run test/unit/crowdsource/
npx vitest run test/unit/notifications/

# With coverage
npx vitest run test/unit/ --coverage
```

## Test Patterns

### Testable Subclass Pattern

For classes with GitHub MCP dependencies, tests use subclasses that allow mock injection:

```javascript
class TestableFeedbackManager extends FeedbackManager {
  constructor(config, mocks = {}) {
    super(config);
    this.mocks = mocks;
  }

  async _createIssue(params) {
    if (this.mocks.createIssue) return this.mocks.createIssue(params);
    throw new Error('Mock not provided');
  }
}
```

### Global Fetch Mocking

For Slack/Email tests that use `fetch`:

```javascript
global.fetch = vi.fn();
global.fetch.mockResolvedValue({ ok: true });
```

### Module Mocking

For NotificationService orchestration tests:

```javascript
vi.mock('../path/to/github-notifier.js', () => ({
  GitHubNotifier: vi.fn().mockImplementation(() => ({
    isEnabled: () => true,
    send: vi.fn().mockResolvedValue({ success: true })
  }))
}));
```