summaryrefslogtreecommitdiff
path: root/tests
AgeCommit message (Collapse)Author
2026-04-06fix: Step 1a validated through TDD — explicit naming + consent bridge ↵Drew Ritter
(PRI-974) Step 1a failed at 2/6 with the spec's original abstract text ("use your native tool"). Three REFACTOR iterations found what works (50/50 runs): 1. Explicit tool naming — "do you have EnterWorktree, WorktreeCreate..." transforms interpretation into factual toolkit check 2. Consent bridge — "user's consent is your authorization" directly addresses EnterWorktree's "ONLY when user explicitly asks" guardrail 3. Red Flag entry naming the specific anti-pattern File split was tested but proven unnecessary — the fix is the Step 1a text quality, not physical separation of git commands. Control test with full 240-line skill (all git commands visible) passed 20/20. Test script updated: supports batch runs (./test.sh green 20), "all" phase, and checks absence of git worktree add (reliable signal) rather than presence of EnterWorktree text (agent sometimes omits tool name). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-06test: add RED/GREEN validation for native worktree preference (PRI-974)Drew Ritter
Gate test for Step 1a — validates agents prefer EnterWorktree over git worktree add on Claude Code. Must pass before skill rewrite. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-25fix(opencode): align skills path across bootstrap, runtime, and testsJesse Vincent
The bootstrap text advertised a configDir-based skills path that didn't match the runtime path (resolved relative to the plugin file). Tests used yet another hardcoded path and referenced a nonexistent lib/ dir. - Remove misleading skills path from bootstrap text; the agent should use the native skill tool, not read files by path - Fix test setup to create a consistent layout matching the plugin's ../../skills resolution - Export SUPERPOWERS_SKILLS_DIR from setup.sh so tests use a single source of truth - Add regression test that bootstrap doesn't advertise the old path - Remove broken cp of nonexistent lib/ directory Fixes #847
2026-03-24Separate brainstorm server content and state into peer directoriesJesse Vincent
The session directory now contains two peers: content/ (HTML served to the browser) and state/ (events, server-info, pid, log). Previously all files shared a single directory, making server state and user interaction data accessible over the /files/ HTTP route. Also fixes stale test assertion ("Waiting for Claude" → "Waiting for the agent"). Reported-By: 吉田仁
2026-03-24Revert "Move brainstorm server metadata to .meta/ subdirectory"Jesse Vincent
This reverts commit ab500dade6187cf78b9b263ecf4799ec3420d1ef.
2026-03-24Move brainstorm server metadata to .meta/ subdirectoryJesse Vincent
Metadata files (.server-info, .events, .server.pid, .server.log, .server-stopped) were stored in the same directory served over HTTP, making them accessible via the /files/ route. They now live in a .meta/ subdirectory that is not web-accessible. Also fixes a stale test assertion ("Waiting for Claude" → "Waiting for the agent"). Reported-By: 吉田仁
2026-03-17fix : resolve ESM/CommonJS module confict in brainstorming serversarbojitrana
2026-03-17fix: Windows brainstorm server lifecycle, restore execution choicejesse
- Skip OWNER_PID monitoring on Windows/MSYS2 where the PID namespace is invisible to Node.js, preventing server self-termination after 60s (#770) - Document run_in_background: true for Claude Code on Windows (#767) - Restore user choice between subagent-driven and inline execution after plan writing; subagent-driven is recommended but no longer mandatory - Add Windows lifecycle test script verified on Windows 11 VM - Note #723 (stop-server.sh reliability) as already fixed Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-15fix: use portable shebang #!/usr/bin/env bash in all shell scriptsjesse
Replace #!/bin/bash with #!/usr/bin/env bash in 13 scripts. The hardcoded path fails on NixOS, FreeBSD, and macOS with Homebrew bash. #!/usr/bin/env bash is the portable POSIX-friendly alternative. Tested on Linux and Windows (Git Bash + CMD). macOS is the primary beneficiary since Homebrew installs bash to /opt/homebrew/bin/bash. Based on #700, closes #700. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-11Add design spec and tests for zero-dep brainstorm serverJesse Vincent
Replace vendored node_modules (714 files) with a single server.js using only Node built-ins. Spec covers WebSocket protocol, HTTP serving, file watching, and static file serving. Tests written before implementation (TDD). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-09Move brainstorm-server into skill directory per agentskills specJesse Vincent
Moves lib/brainstorm-server/ → skills/brainstorming/scripts/ so the brainstorming skill uses relative paths (scripts/start-server.sh) instead of ${CLAUDE_PLUGIN_ROOT}/lib/brainstorm-server/. This follows the agentskills.io specification for portable, cross-platform skills. Updates visual-companion.md references and test paths. All tests pass.
2026-03-09chore: remove dead lib/skills-core.js and its testsJesse Vincent
Last consumer (Codex bootstrap CLI) was removed on 2026-02-05. Removes the library, its dedicated test file, and references in test-plugin-loading.sh and run-tests.sh. h/t @RomarQ (PR #525) for flagging this.
2026-03-09fix: replace bare except with except Exceptiondaniel-graham
Co-authored-by: daniel-graham <daniel-graham@users.noreply.github.com>
2026-03-06Add end-to-end tests for document review systemJesse Vincent
2026-03-06refactor: restructure specs and plans directoriesJesse Vincent
- Specs (brainstorming output) now go to docs/superpowers/specs/ - Plans (writing-plans output) now go to docs/superpowers/plans/ - User preferences for locations override these defaults - Update all skill references and test files Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-03-06Add brainstorm server with WebSocket support, helpers, and testsJesse Vincent
WebSocket server for real-time browser communication during brainstorming sessions. Includes browser helper library for event capture, shell scripts for server lifecycle management with session isolation and persistent mockup storage, and integration tests. Co-Authored-By: Drew Ritter <drew@ritter.dev>
2026-02-11Fix stream-json output requiring --verbose flagchengfei.jin
Claude CLI now requires --verbose when using --output-format stream-json with -p (print mode). Without it, the test fails with: "Error: When using --print, --output-format=stream-json requires --verbose"
2026-01-29docs: change main branch red flag to require explicit user consentCL Kao
Instead of prohibiting main branch work entirely, allow it with explicit user consent. This is more flexible while still ensuring users are aware of the implications. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-29test: add Test 9 - main branch red flag warningCL Kao
TDD: Test verifies that subagent-driven-development skill warns against starting implementation directly on main/master branch. Test expects skill to recommend worktree or feature branch instead. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-29test: add worktree requirement test for subagent-driven-developmentCL Kao
Add Test 8 to verify that using-git-worktrees is mentioned as a required skill for subagent-driven-development. This test will initially fail per TDD approach - the skill file needs to be updated to pass this test. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-29fix(tests): handle case variations in skill recognition testCL Kao
The assertion now matches "subagent-driven-development", "Subagent-Driven Development", and "Subagent Driven" since Claude's responses may use different casing and formatting styles. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-23fix(opencode): standardize on plugins/ directory per official docsJesse Vincent
OpenCode officially documents ~/.config/opencode/plugins/ (plural) as the plugin directory. Our docs previously used plugin/ (singular), which also works but caused confusion. Changes: - Renamed .opencode/plugin/ to .opencode/plugins/ in repo structure - Updated INSTALL.md to use plugins/ everywhere - Updated README.opencode.md (all platforms: Linux, macOS, Windows CMD, PowerShell, Git Bash) to use plugins/ - Updated test scripts to match Tested: Both singular and plural forms work, but we now match official docs. Fixes #343 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2025-12-26Strengthen using-superpowers for explicit skill requestsJesse Vincent
Addresses failure mode where Claude skips skill invocation even when user explicitly requests it by name (e.g., "subagent-driven-development, please"). Skill changes: - "Check for skills" → "Invoke relevant or requested skills" - "BEFORE ANY RESPONSE" → "BEFORE any response or action" - Added reassurance that wrong skill invocations are okay - New red flag: "I know what that means" Tests: - New test suite for explicit skill requests - Single-turn and multi-turn scenarios with --continue - Tests with haiku model and user CLAUDE.md
2025-12-17Add skill triggering test frameworkJesse Vincent
Creates tests/skill-triggering/ to validate skills trigger correctly from naive prompts (without explicitly naming the skill). Tests 6 skills: - systematic-debugging - test-driven-development - writing-plans - dispatching-parallel-agents - executing-plans - requesting-code-review All 6 tests pass - skills trigger correctly based on their descriptions.
2025-12-17Document skill description trap: descriptions override flowchartsJesse Vincent
Testing revealed that skill descriptions summarizing workflow cause Claude to follow the description instead of reading the skill body. - A description saying "code review between tasks" caused ONE review - The flowchart clearly showed TWO reviews (spec compliance + quality) - Minimal description ("Use when...") correctly deferred to flowchart Updated writing-skills with: - "Description = When to Use, NOT What the Skill Does" section - Cautionary tale about this actual failure - Examples of good (triggers only) vs bad (workflow summary) descriptions Updated subagent-driven-development: - Removed workflow summary from description - Now just: "Use when executing implementation plans..." Updated test runner: - Added --dangerously-skip-permissions for automated testing
2025-12-17Add .claude settings to scaffolds for auto-approved permissionsJesse Vincent
2025-12-17Add test suite for subagent-driven-development skillJesse Vincent
Two test projects for validating the skill with full end-to-end runs: - go-fractals: 10 tasks, CLI tool with Sierpinski and Mandelbrot - svelte-todo: 12 tasks, CRUD app with localStorage and Playwright Each test has design.md, plan.md, and scaffold.sh. Run with: ./tests/subagent-driven-dev/run-test.sh go-fractals
2025-12-17Add token usage analysis to subagent-driven-development testJesse Vincent
- Rewrote analyze-token-usage.py to parse main session file correctly - Extracts usage from toolUseResult fields for each subagent - Shows breakdown by agent with descriptions - Integrated into test-subagent-driven-development-integration.sh - Displays token usage automatically after each test run
2025-12-17fix: verify skill usage via session transcript not text outputJesse Vincent
The skill instructions are internal and don't appear in user-facing output. Updated verification to parse the session JSONL transcript and check for actual tool usage: - Skill tool invocation - Task tool (subagents) - TodoWrite (tracking) - Implementation results
2025-12-17test: use bypassPermissions mode for unrestricted testingJesse Vincent
dontAsk mode was auto-denying Write tool. Use bypassPermissions instead to allow full tool access in this controlled test environment.
2025-12-17test: auto-approve permissions with --permission-mode dontAskJesse Vincent
Headless tests need automatic permission approval to write files. Using dontAsk mode to auto-approve permissions for test directory.
2025-12-17test: add --add-dir flag for temp directory accessJesse Vincent
Claude needs explicit permission to access the temp test directory. Added --add-dir flag to grant access to the test project.
2025-12-17test: show Claude output in real-time during integration testJesse Vincent
Use tee instead of redirection so test output is visible during execution while still being saved to file for analysis.
2025-12-17fix: run integration test from superpowers dir to access local dev skillsJesse Vincent
The superpowers-dev marketplace makes skills available only when running from the plugin directory. Updated test to run claude from superpowers directory while working on the test project.
2025-12-17Fix tests to use --allowed-tools flagJesse Vincent
Claude Code headless mode requires --allowed-tools flag to actually execute tool calls. Without it, Claude only responds as if it's doing things but doesn't actually use tools. Changes: - Updated run_claude helper to accept allowed_tools parameter - Updated integration test to use --allowed-tools=all - This enables actual tool execution (Write, Task, Bash, etc.) Now the integration test should actually execute the workflow instead of just talking about it.
2025-12-17Fix syntax error in integration testJesse Vincent
Simplified command substitution to avoid shell parsing issues. Instead of nested heredoc in command substitution, write prompt to file first then read it.
2025-12-17Add integration test for subagent-driven-developmentJesse Vincent
Created full end-to-end integration test that executes a real plan and verifies the new workflow improvements actually work. New test: test-subagent-driven-development-integration.sh - Creates real Node.js test project - Generates implementation plan (2 tasks) - Executes using subagent-driven-development skill - Verifies 8 key behaviors: 1. Plan read once at beginning (not per task) 2. Full task text provided to subagents (not file reading) 3. Subagents perform self-review 4. Spec compliance review before code quality 5. Spec reviewer reads code independently 6. Working implementation produced 7. Tests pass 8. No extra features added (spec compliance) Integration tests are opt-in (--integration flag) due to 10-30 min runtime. Updated run-skill-tests.sh: - Added --integration flag - Separates fast tests from integration tests - Shows note when integration tests skipped Updated README with integration test documentation. Run with: ./run-skill-tests.sh # Fast tests only ./run-skill-tests.sh --integration # Include integration tests
2025-12-17Add Claude Code skills test frameworkJesse Vincent
Created automated test suite for testing superpowers skills using Claude Code CLI in headless mode. New files: - tests/claude-code/run-skill-tests.sh - Main test runner - tests/claude-code/test-helpers.sh - Helper functions for testing - tests/claude-code/test-subagent-driven-development.sh - First test - tests/claude-code/README.md - Documentation Test framework features: - Run Claude Code with prompts and capture output - Assertion helpers (contains, not_contains, count, order) - Test project creation helpers - Timeout support (default 5 minutes) - Verbose mode for debugging - Specific test selection First test verifies subagent-driven-development skill: - Skill loading - Workflow ordering (spec compliance before code quality) - Self-review requirements - Plan reading efficiency (read once) - Spec compliance reviewer skepticism - Review loops - Task context provision Run with: cd tests/claude-code && ./run-skill-tests.sh
2025-11-24fix: cleanup remaining code review issuesClaude
- Remove unused destructured parameters (project, $, worktree) from plugin - Add test coverage for checkForUpdates function (error handling cases)
2025-11-23fix: address code review issues in opencode support branchClaude
- Fix test runner exiting early due to ((var++)) returning 1 with set -e - Remove duplicate frontmatter stripping in superpowers-codex, use shared skillsCore.stripFrontmatter() - Remove unused promptsDir/promptFile variables from opencode plugin - Derive superpowers skills path from __dirname for better install flexibility - Simplify test-skills-core.sh by removing failing ESM import attempt
2025-11-23fix: add OPENCODE_CONFIG_DIR for proper test isolationJesse Vincent
2025-11-23test: add automated test suite for opencode pluginJesse Vincent
Create comprehensive tests in tests/opencode/ that verify the plugin works correctly in an isolated test environment: - setup.sh: Creates temp HOME and installs plugin with proper symlinks - test-plugin-loading.sh: Verifies plugin structure and JavaScript syntax - test-skills-core.sh: Unit tests for skills-core.js library functions - test-tools.sh: Integration tests for use_skill/find_skills (requires OpenCode) - test-priority.sh: Tests project > personal > superpowers priority - run-tests.sh: Main test runner with options for integration tests Run basic tests: ./tests/opencode/run-tests.sh Run all tests: ./tests/opencode/run-tests.sh --integration