Getting started
Install StrikeTest and write your first .stk test
StrikeTest test files use the .stk extension. Scenarios read like acceptance criteria and run against real browsers (web) or Appium (mobile).
After installation, continue with First test, then Suite manifest (main.json) when you split flows across files. See the Language guide and full Commands / Qualifiers references.
Path
- Install with the GUI installer (agent + runner + browsers)
- Pair this computer in the web app (Run tests)
- Write and run a first test
- Organize files with
main.json(optional — multi-file suites) - Set up the editor extension (optional)
- Connect the production MCP (optional — Cursor agent authoring)
What you will use
| Piece | Purpose |
|---|---|
| Web app | Manage projects, pair, start runs, view reports |
| strikekit-agent | Local background service (127.0.0.1:19527) |
| strikekit runner | Executes .stk / main.json tests |
.stk suites | Plain-English scenarios |
| STK extension | Completion, diagnostics, format in VS Code / Cursor (optional) |
| Knowledge MCP | Hosted Cursor MCP (production catalog) for .stk drafting |