Tryke for VS Code
VS Code integration for Tryke — a fast Rust-powered test runner for Python.
Tests show up in the native VS Code Test Explorer. Run, debug, and watch tests with inline pass/fail gutter decorations and per-assertion diagnostics routed through Tryke's JSON event stream.
Requirements
- Tryke installed and on
PATH (or set tryke.command to its full path).
- A workspace containing a
pyproject.toml.
Install Tryke with your package manager of choice:
uv add --dev tryke
# or
pip install tryke
See the Tryke docs for writing tests.
Features
- Test Explorer integration — discover, run, and debug Tryke tests from the VS Code sidebar.
@test.cases parametrized tests — each case (square[zero], square[one], …) appears as its own item with full fidelity.- Server mode — reuses a long-running
tryke server process for near-instant reruns. The extension auto-starts and manages its lifecycle.
- Direct mode — falls back to spawning
tryke test per run when a server isn't available.
- Watch mode session — streams results from
tryke as files change.
- Changed-files runs — optionally limit runs to tests affected by your git diff.
- Dedicated output channels —
Tryke for extension activity, Tryke Server for piped server stdout/stderr.
Commands
| Command |
ID |
| Tryke: Start Server |
tryke.startServer |
| Tryke: Stop Server |
tryke.stopServer |
| Tryke: Restart Server |
tryke.restartServer |
Settings
| Setting |
Default |
Description |
tryke.command |
tryke |
Path to the tryke executable. |
tryke.mode |
auto |
Runner mode: direct, server, or auto. |
tryke.server.host |
127.0.0.1 |
Tryke server host. |
tryke.server.port |
2337 |
Tryke server port. |
tryke.server.autoStart |
true |
Auto-start the server when using server mode. |
tryke.server.autoStop |
true |
Stop the server on extension deactivation. |
tryke.workers |
null |
Number of worker threads (-j). |
tryke.failFast |
false |
Stop after the first failure (--fail-fast). |
tryke.maxfail |
null |
Stop after N failures (--maxfail). |
tryke.dist |
null |
Work distribution (test, file, group). |
tryke.markers |
null |
Tag/marker filter (-m). |
tryke.changed |
off |
Run only --changed tests, --changed-first, or off. |
tryke.baseBranch |
null |
Base branch for changed-file detection. |
tryke.args |
[] |
Extra arguments forwarded to tryke. |
Parametrized tests
@test.cases functions show up as one Test Explorer item per case label. Discovery reads tryke --collect-only JSON output, so both dict and list forms map through unchanged:
@test.cases(
zero={"n": 0, "expected": 0},
one={"n": 1, "expected": 1},
ten={"n": 10, "expected": 100},
)
def square(n: int, expected: int) -> None:
expect(n * n).to_equal(expected)
The tree shows square[zero], square[one], square[ten]. Running an individual case dispatches tryke test … -k 'square[zero]', and per-case test_complete events map back to the matching tree item by label.
License
MIT
