DEMO / RECORDING
Overview & result
Jevcumber turns Gherkin browser-test steps into Playwright actions without hand-written step definitions. Jev chooses among controls actually present on the page and literal values from the step; a lockfile makes later runs deterministic.
From the original post
Write Cucumber tests with just the `.feature` file. No step definitions.
How Jev fits in the loop
- Open the target page with Playwright and enumerate buttons, fields, links and literal values from the feature step.
- Ask Jev in one request to choose the action type, target, input and whether to submit.
- Refuse low-confidence matches, execute with Playwright and save the resolved step in a lockfile.
How to reproduce
- Install the package and browser; run the repository's frozen example without an API key.
- For a new `.feature` file, set `TYPESAFE_API_KEY` and resolve steps against a live page.
- Commit and review the generated `.feature.lock.json`; use frozen replay to avoid repeat model calls.
Why this build matters
A clear Jev role in browser automation: select bounded actions, then let deterministic code execute and replay them.
Limitations
- Low-confidence target matches stop for clarification instead of guessing.
- A frozen lockfile avoids new Jev calls, but changed UI controls may require re-resolution.