Precision QA, managed in the cloud — executed on your machine.
Organize versioned plain-English .stk suites, run them locally via strikekit-agent, and share proof across your team.
The idea
Cloud-managed suites. Local execution. Shared proof.
You work in the web app. A local agent pairs your computer, syncs versioned suites, and starts the runner behind your firewall — results stream back as live pass/fail.
- 01
Author in plain English
Labels, not selectors. Steps read like acceptance criteria — fill, click, should, wait.
- 02
Run where the app lives
strikekit-agent on localhost syncs suites and launches the runner on your machine — not in Strikekit’s cloud by default.
- 03
Share proof with the team
Live NDJSON during the run, ReportV1 afterward — so QA and product see the same outcome.
The language
Tests that product and QA can both read.
One file, one platform. Scenarios use Given / When / Then with quoted labels. Start with Getting started, then dive into commands and complex flow examples.
Group: Authentication
Scenario: User login @smoke
Given I navigate to "$BASE_URL/login"
When I fill "username" with "chamodh"
And I fill "password" with "1234"
And I click on "Login"
Then I should see "Welcome back"Documentation