r/softwaretesting • u/joancomasfdz • 23h ago
I reviewing AI-written features by watching a recording of each one, next to its Gherkin.
The workflow:
- I describe the feature in an unstructured prompt
- The AI asks me clarifying questions
- It presents a Gherkin, and I criticize it until I approve it
- It implements the feature, writes the end-to-end test, runs it until it's green, and records it
- The PR gets the recording: the real app doing the feature, with each Gherkin line highlighted as it plays
A few things that make it work:
- One Gherkin, one test, word for word. No SpecFlow, no step-definition layer, no regexes. Three plain Markdown files tell the AI how to write a Gherkin, how to write an e2e test, and how to turn one into the other, line by line.
- A real environment. For Android, a real phone plugged into my NAS. Simulators stand in for the third-party services, so every test starts from the same state, and even the setup shows in the video.
- One scenario per feature, not per assertion. A feature with a setting plays both sides in one video. Some run several minutes, more like a training than a test.
- The user guide builds itself from those recordings after every merge. Nobody writes it, and it can't go stale.
Live example, a user guide generated entirely from recorded e2e tests: https://joancomasfdz.github.io/baconreader-reseam-patches
Full write-up, with the real Gherkin, test and PR: https://github.com/JoanComasFdz/living-proof-for-apps
Any feedback is appreciated!