feat(marketplace): command consolidation + 8 new plugins (v8.1.0 → v9.0.0) [BREAKING]
Phase 1b: Rename all ~94 commands across 12 plugins to /<noun> <action> sub-command pattern. Git-flow consolidated from 8→5 commands (commit variants absorbed into --push/--merge/--sync flags). Dispatch files, name: frontmatter, and cross-reference updates for all plugins. Phase 2: Design documents for 8 new plugins in docs/designs/. Phase 3: Scaffold 8 new plugins — saas-api-platform, saas-db-migrate, saas-react-platform, saas-test-pilot, data-seed, ops-release-manager, ops-deploy-pipeline, debug-mcp. Each with plugin.json, commands, agents, skills, README, and claude-md-integration. Marketplace grows from 12→20. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
36
plugins/saas-test-pilot/claude-md-integration.md
Normal file
36
plugins/saas-test-pilot/claude-md-integration.md
Normal file
@@ -0,0 +1,36 @@
|
||||
# Test Pilot Integration
|
||||
|
||||
Add to your project's CLAUDE.md:
|
||||
|
||||
## Test Automation
|
||||
|
||||
This project uses saas-test-pilot for test generation and coverage analysis.
|
||||
|
||||
### Commands
|
||||
- `/test setup` - Detect framework and configure test environment
|
||||
- `/test generate <target>` - Generate tests for a function, class, or module
|
||||
- `/test coverage` - Analyze coverage gaps prioritized by risk
|
||||
- `/test fixtures generate <model>` - Create fixtures and factories
|
||||
- `/test e2e <feature>` - Generate E2E test scenarios
|
||||
- `/test run` - Execute tests with formatted output
|
||||
|
||||
### Supported Frameworks
|
||||
- Python: pytest, unittest
|
||||
- JavaScript/TypeScript: Jest, Vitest
|
||||
- E2E: Playwright, Cypress
|
||||
|
||||
### Test Organization
|
||||
Tests follow the standard structure:
|
||||
```
|
||||
tests/
|
||||
conftest.py # Shared fixtures
|
||||
unit/ # Unit tests (fast, isolated)
|
||||
integration/ # Integration tests (database, APIs)
|
||||
e2e/ # End-to-end tests (browser, full stack)
|
||||
fixtures/ # Shared test data and response mocks
|
||||
```
|
||||
|
||||
### Coverage Targets
|
||||
- coverage-analyst provides risk-based gap analysis
|
||||
- Focus on branch coverage, not just line coverage
|
||||
- Critical modules (auth, payments) require higher thresholds
|
||||
Reference in New Issue
Block a user