Cloud suites. Local execution.
Upload versioned .stk files, pair strikekit-agent on your machine, and run Playwright-backed tests with live results and shared JSON reports.
Your QA journey
Six steps from sign-up to shared proof — cloud-managed .stk suites with local execution via strikekit-agent.
Sign up and join your organization
Create a Strikekit account, verify your email, then create an organization or accept a team invitation.
- Onboarding: create org or join via invite
- Multi-tenant workspace with RBAC
Create projects and upload .stk versions
Organize work under workspaces and projects. Upload versioned .stk suite files, main.json manifests, and assets to cloud storage.
- Semver version keys per project
- Playwright-backed suites via the strikekit runner
Install agent and runner
Two separate binaries: strikekit-agent (background localhost service) and the strikekit runner (executes tests). The agent has no desktop UI — you stay in the browser.
- Agent listens on 127.0.0.1:19527 only
- Runner default: /usr/local/bin/strikekit
Pair this computer
From the Run tests dashboard, click Pair this computer. Your browser links to the local agent via a secure pairing code — no exposed internal ports.
- Entry point: Run tests in the dashboard
- Re-pair after agent upgrades or config changes
Sync & run or Local folder
Choose Sync & run to pull a cloud version to your machine, or Local folder to execute from a custom directory on disk. The agent spawns strikekit run main.json and streams NDJSON live.
- Sync & run: cloud .stk → local agent → run
- Local folder: skip cloud download, use saved path
Upload reports and share proof
After a run, upload ReportV1 JSON to the cloud. View step-level pass/fail, errors, and export results. Optionally link runs to Jira QA tickets.
- Reports list, view, and Excel export
- Optional issueKey linkage when Jira is connected
Two ways to run
Both modes execute locally via strikekit run main.json and stream NDJSON results to the Run tests dashboard in real time.
Sync & run
Select a project and semver version from the dashboard. The browser downloads .stk files from the cloud and relays them to strikekit-agent, which writes them under ~/.strikekit/projects/{projectId}/ before running.
- Cloud is the source of truth for suite versions
- SHA-256 diff sync — only changed files transfer
- Best for teams sharing the same suite versions
Local folder
Run tests from a directory on disk without downloading cloud files. Pick a folder via the agent or enter a path manually. Cloud versions remain available if you uploaded them separately.
- Skips cloud file download at run time
- Requires allow_custom_paths in agent config
- Linux browse: zenity or kdialog, or enter path manually
What makes up Strikekit
Four pieces work together: the runner binary executes tests locally, the agent bridges your machine, the web UI controls runs in the browser, and the backend stores suites and reports.
Execution path
Runner binary
strikekit — executes tests
Agent
strikekit-agent on localhost
Web UI
Browser dashboard
Backend
Cloud API + storage
Runner binary
strikekit
The local CLI that runs Playwright-backed suites. Invoked as strikekit run main.json, it executes steps and streams live NDJSON events (pass, fail, logs) to stdout.
- Separate binary from the agent
- Default path: /usr/local/bin/strikekit
- Produces step-level results for the dashboard
Agent
strikekit-agent
A background service on your machine — not a desktop app. It pairs with the browser, syncs .stk files, spawns the runner, and relays WebSocket streams. Listens on 127.0.0.1:19527 only.
- Pairs via short-lived codes from the cloud
- Syncs suites under ~/.strikekit/projects/
- Never accepts inbound network connections
Web UI
frontend-user dashboard
The browser app where you manage organizations, projects, versions, and runs. From Run tests you pair this computer, choose Sync & run or Local folder, and watch live results.
- Talks to the backend for data and auth
- Talks to the agent on localhost for execution
- Uploads ReportV1 JSON after a run
Backend
Cloud API
The multi-tenant API and storage layer. It owns orgs, RBAC, versioned .stk suites, pairing codes, and reports — so teams share suites and proof without exposing local machines.
- Stores .stk versions and ReportV1 results
- Issues pairing codes redeemed by the agent
- Optional Jira linkage for QA tickets
Jira QA ticket loop
Connect Jira to sync tickets, run tests against linked issues, and upload reports as shared proof — without leaving your QA dashboard.
Connect in Settings
From Settings → Integrations, connect Jira via OAuth. Available on plans with the Jira feature entitlement.
QA queue sync
Tickets sync from configured Jira statuses into the QA queue. Run tests linked to a ticket via issueKey.
Transitions and reports
Move tickets through Jira workflows from Strikekit. Uploaded ReportV1 JSON can be tied to the linked issue.
Technical details
Accurate answers about local execution, storage, and integrations.
Ready to run your first test?
Join QA and engineering teams who unified their testing workflow with Strikekit. Start your 14-day free trial — no credit card required.