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/testDetects project type and runs the appropriate test suite (pytest, npm test, mvn test, gradle test, dotnet test, go test, cargo test). Reports pass/fail counts and failure details.
/run-testsExecutes tests with auto-detected framework (Jest, Vitest, pytest, Go test) and optional type/flags. Reports pass/fail counts, time, and coverage.
/test-fileGenerates unit tests for a specified file, including edge cases and error scenarios, following the project's existing testing framework and conventions.
/testRuns a test-driven development workflow for new features and bug fixes, writing failing tests first then implementing and verifying; also supports the Prove-It pattern for bug reproduction.
/testRuns tests for a CLI harness using pytest, captures full output, verifies subprocess backend, and updates TEST.md with results and pass/fail summary.
/testDiscovers and runs unit, integration, or e2e tests with coverage analysis, failure diagnostics, and quality reporting. Supports watch mode and Playwright-based browser testing.