test-framework-detectorlisted

# Test Framework Detector ## Purpose Automatically identify which test framework(s) a project uses by examining: - Package manifests (package.json, requirements.txt, Gemfile, *.csproj) - Test configuration files (jest.config.js, pytest.ini, spec_helper.rb, xunit.runner.json) - Directory structure and naming conventions ## Usage This skill is invoked by agents (like deep-debugger) when they need to determine which test framework to use for test generation or execution. ### Detection Script Run the detection script with the project path: ```bash node detect-framework.js /path/to/project ``` ### Output Format The script returns a JSON object with detected frameworks: ```json { "detected": true, "frameworks": [ { "name": "jest", "confidence": 0.95, "version": "29.7.0", "configFiles": ["jest.config.js", "package.json"], "testDirectory": "tests/", "testPattern": "**/*.test.js" } ], "primary": "jest" } ``` ## Detection Patterns The skill uses pattern-based detection defined in `framework-patterns.json`. Each framework has: - **Package indicators**: Dependencies that suggest framework presence - **Config files**: Framework-specific configuration files - **Test file patterns**: Common test file naming conventions ## Supported Frameworks 1. **Jest** (JavaScript/TypeScript) - Config: jest.config.js, jest.config.ts, package.json (jest section) - Dependencies: jest, @types/jest, ts-jest - Patterns: *.test.js, *.spe