History

Brian Madison b37ca3b314 fix(config): promote project_name to core, fixes #2279 project_name was a bmm-specific prompt despite being a universal project-level concept used by every module — including core skills like bmad-brainstorming, which loads from _bmad/core/config.yaml and was silently broken because project_name lived under bmm. Users without bmm installed could not run brainstorming at all. Move: - src/core-skills/module.yaml: declare project_name with prompt "What is your project called?" and default {directory_name}, matching what bmm previously had. - src/bmm-skills/module.yaml: remove the bmm definition; add project_name to the "Variables from Core Config inserted" header comment so contributors can see what's inherited. Migration for existing installs: - tools/installer/modules/official-modules.js: after loadExistingConfig reads each per-module config.yaml, hoist any keys that are now declared in core but appear under non-core modules. Without this, the partition logic in writeCentralConfig (which strips core keys from non-core buckets) would silently drop the user's prior project_name on the next quick-update. Generic — handles project_name today and any future module→core promotions. - The hoist preserves precedence: an existing core value beats a stale module-side copy. --yes seed: - tools/installer/ui.js: add project_name to the hardcoded core seed (using path.basename(directory) to match the {directory_name} default) so non-interactive fresh installs populate it. Without this the seed silently omits project_name and core skills fall back to literals. Tests: - test/test-installation-components.js Suite 43 (9 assertions) covers the schema move, the loadExistingConfig hoist, and the precedence rule. - Suite 35 fixture updated: project_name moved from bmm bucket to core, with a stale bmm copy left in place to verify it gets stripped. Verified manually: - Fresh install -y: project_name lands in [core] of config.toml. - Existing install with project_name in bmm/config.yaml: quick-update hoists it to [core] and strips it from [modules.bmm].		2026-04-27 23:20:52 -05:00
..
adversarial-review-tests	feat(tasks): convert review-adversarial-general XML task to native skill (#1857 )	2026-03-08 06:52:55 -06:00
fixtures/file-refs-csv	chore: remove dead agent schema validation infrastructure	2026-03-17 20:20:12 -06:00
README.md	chore: remove dead agent schema validation infrastructure	2026-03-17 20:20:12 -06:00
test-file-refs-csv.js	refactor(skills): convert party-mode to native skill directory (#1906 )	2026-03-11 22:48:29 -05:00
test-installation-components.js	fix(config): promote project_name to core, fixes #2279	2026-04-27 23:20:52 -05:00
test-installer-channels.js	feat(installer): channel-based version resolution + interactive channel management (#2305 )	2026-04-24 08:20:30 -05:00
test-rehype-plugins.mjs	fix(docs): comprehensive documentation site review fixes (#1578 )	2026-02-08 11:58:22 -06:00
test-workflow-path-regex.js	refactor(installer): restructure installer with clean separation of concerns (#2129 )	2026-03-27 06:50:07 -06:00

README.md

Test Suite

Tests for the BMAD-METHOD tooling infrastructure.

Quick Start

# Run all quality checks
npm run quality

# Run individual test suites
npm run test:install    # Installation component tests
npm run test:refs       # File reference CSV tests
npm run validate:refs   # File reference validation (strict)

Test Scripts

Installation Component Tests

File: test/test-installation-components.js

Validates that the installer compiles and assembles agents correctly.

File Reference Tests

File: test/test-file-refs-csv.js

Tests the CSV-based file reference validation logic.

Test Fixtures

Located in test/fixtures/:

test/fixtures/
└── file-refs-csv/    # Fixtures for file reference CSV tests