From wink
Runs the project's configured test command from .winkclaude/config.json verifiers.test (e.g., go test ./...).
How this command is triggered — by the user, by Claude, or both
Slash command
/wink:testThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Run Tests
Run the configured test command for this project.
Configurable in `.winkclaude/config.json`:
Run: bun ${CLAUDE_PLUGIN_ROOT}/dist/commands/test.jsRun the configured test command for this project.
Configurable in .winkclaude/config.json:
{
"verifiers": {
"test": "go test ./..."
}
}
Run: bun ${CLAUDE_PLUGIN_ROOT}/dist/commands/test.js
npx claudepluginhub joshuarweaver/cascade-code-testing-misc --plugin skishore23-wink/testRuns project test suite by auto-detecting type (Python, Node.js, Java, .NET, Go, Rust) and executing tests (pytest, npm test, mvn test, etc.). Reports pass/fail, details failures, suggests fixes.
/testRuns a TDD workflow: write failing tests, implement code, and verify. For bug fixes, uses the Prove-It pattern to reproduce, fix, and confirm.
/testRuns pytest tests for CLI harness on local path or GitHub repo, verifies CLI resolution, and updates TEST.md with results if all pass.
/testExecutes unit, integration, or e2e tests with coverage analysis, quality metrics, failure diagnostics, and optional watch mode or auto-fixes.
/testGenerates test strategy overview, unit and integration test code, coverage analysis, execution plan, and maintenance roadmap for a specified component or feature.
/testLaunches Chrome for manual UI testing at given URL, monitors console errors during interaction, generates report with screenshots and logs on completion.