Test leads
Set the writing standard once and stop re-explaining it in every pull request.
Gherkin, treated like source
A studio for your .feature files.
Feature files are the one artefact your testers, developers and business people — your Three Amigos — all read, written for Cucumber and every other Gherkin-based BDD framework. It's also the one thing every test automation suite eventually outgrows anyone's ability to hold in their head. CukesStudio gives them a home: a linting editor that holds every scenario to your house standard, a review workflow that gets them signed off, and a way to see, across thousands of scenarios, which ones actually matter.
No install. Bring your own .feature files.
01 — Write
A house standard, enforced while you type.
Every BDD team has rules about how a scenario should read. CukesStudio knows them: declarative steps over UI clicks, one behaviour per scenario, backgrounds that actually set context. Violations surface in the gutter as you write, and rules you disagree with can be switched off — it's your standard, not ours.
- Syntax errors and writing-standard violations, separated
- Suppress a violation in place when the rule genuinely doesn't apply
- Read, Review and Edit modes, so nobody changes a file by accident
02 — Review
Sign-off that leaves a trail.
A feature file moves from new, to in review, to accepted — or gets rejected with the reviewer's name against it. Set how many approvals your team needs. Team leads can accept outright. Anything still being written gets parked as a draft, tagged @WIP in the file itself so your runner skips it.
- Configurable approval threshold, per team
- Team leads accept outright; anyone can approve or reject
- A dashboard that opens on what's waiting for you
03 — Plan
Untagged doesn't stay small.
A suite starts out small enough to hold in your head. Then it's hundreds of scenarios, written by different people over different sprints, and nobody agreed on what's smoke, what's regression, and what's neither — so "we should really tag these" quietly never happens. Plan puts every scenario in the workspace on one screen, grouped by feature, and tags them smoke, regression or extended with a click — one scope per scenario, plus as many of your own tags underneath as you actually group by — writing straight into the feature file, where Cucumber (or whatever runs your suite) will find it. Same screen whether the workspace holds a dozen scenarios or ten thousand.
- Live counts and filters across the whole workspace, however large it gets
- Tagging is a five-second decision made where the scenario lives, not a separate triage project
- Tags land in the file, not in a database only CukesStudio can read
- Two people can tag at once without overwriting each other
Built for the people who own the feature files
BDD coaches
Show a team what good looks like while they type, instead of after they've written it.
Delivery teams
Run your Three Amigos sessions here — get business sign-off on the scenarios before anyone automates the wrong behaviour.
Automation engineers
Keep test automation suites maintained sprint after sprint as the project grows, so living documentation stays accurate for the wider team.
Already set up?
Sign in to the shared app — the same CukesStudio your team's workspaces already live in.
Sign inTry it with your own features.
The demo is a full copy of CukesStudio. Sign yourself up, upload your own .feature files, and see what the linter makes of them. Nothing you put there is permanent — the demo is wiped regularly.
Open the demoWant your own?
Teams that want to keep their work get their own instance at yourcompany.cukesstudio.com — your workspaces, your teams, your standard, separate from everyone else's.
Or run it yourself.
A Docker Compose stack for teams that keep everything on their own infrastructure — nothing you write ever reaches CukesStudio's servers. Same editor, same linter, your own Postgres.
Get the self-hosted stack