Groma

Precision-guided manual test runner. Author a flow as a shareable spec, then run it guided with a human as the sole arbiter.

Groma is a precision-guided manual test runner. A QA/PM authors a flow by walking the app once; Groma captures it as a spec that travels inside a link. Anyone that link reaches runs the flow guided, with Groma spotlighting each step — but the human stays the sole arbiter of every result. Nothing auto-passes or auto-fails. Author Click the Groma icon and walk your app normally. Groma docks in the browser's side panel and captures the navigation plus a resilient, layered locator for every element you point it at (test ID → id → name → role → label → link → text → row-scoped → structural fallback), naming each pick from what it found. You write the checkpoint's instruction and expected result. Nothing is captured until you ask for it — arm the picker, then click the element. It works on staging, prod, or localhost without touching your app's source, because the content script has the same same-origin DOM access your browser does. A microphone icon lets you dictate instructions and expected results instead of typing, using your browser's own speech recognition. A spec that is a variation on one you already wrote — the same checkout signed in, the same form with bad data — is duplicated with one click and edited, instead of walked again. The row's arrows put the specs in the order they should run in. Stop halfway and the draft is kept for you; the panel offers it back next time you open it. A step you have already written — a sign-in, a cookie banner, getting to the right account — is linked in from another spec instead of retyped, searchable by spec name or by the words in the step. It comes across as a copy, so editing it never reaches back into the spec it came from, and it keeps one button to re-read it from there if you want to. Keep your specs as files, in a folder you own Point Groma at a folder and every spec is saved into it as one plain JSON file. That folder is yours: put it in a git repo and your specs get diffs, review and branches beside the code they describe; put it in a synced folder and they sync. Groma has no account, no sign-in and no server, and doesn't know or care which you chose. Connect more than one — a client's app, an internal tool, separate staging and production sets — and switch between them with a click. Groma's Home page lists everything in the active one, grouped by the document it belongs to, with a step count and a rough length, a read-only preview of what each spec asks a tester to do, the order the specs run in, and every past run of each spec. Edit one and it opens in the side panel and saves straight back. Tick a few, name the document, say which server it runs against, and Share builds a file for a tester that holds run links only — no edit link, so it can be forwarded freely. Test the mobile layout without a second document Any step can be written for a screen size. Resize your own browser until the layout you want is on screen — the panel names the width as you drag — and press Set size on that step. When a tester reaches it, their window is put to that width, so one spec can walk them through a mobile drawer and then a desktop table. Nothing is emulated and no debugging permission is asked for: it is your real browser window at a real width. Log what you see Authoring is itself a test pass, so anything wrong you notice on the way has somewhere to go. Log a finding in one click, point it at the element it's about, and let the app's own uncaught errors be logged alongside. Findings never become part of a spec and never reach a tester — they copy out as Markdown for a bug tracker, and download as their own file beside the specs. Run A tester opens the shared link and the app opens in an ordinary tab, with each step beside it in the browser's own side panel and the target spotlighted in place. Pass or Fail — one click each, the step's own note box as the comment, and a screenshot kept for a Fail. There is no third verdict to classify and nothing to pause: Terminate leaves on any step, keeping every verdict already given and counting the steps below it rather than judging them. A run survives a page reload, and a closed side panel, and resumes on the step it left off — and a tester who has to stop for the day parks the whole run with one click and picks it back up on the step they left, even after restarting the browser. Running a whole set in sequence ("Run all") lets the tester tick which of the document's specs actually apply this time and reorder them first, then walks them with nothing to click in between and ends with one archive download. If it's interrupted instead — a closed tab, a crash, a declined download — the finished reports stay parked locally and the toolbar icon badges to say so, so nothing already tested is silently lost. Anything saved — an unfinished draft, a parked run, undelivered reports — is offered back on Groma's home screen, one click from any panel. Share Authoring produces a standalone HTML document listing every spec — no server, no sign-in. Each spec's title is a run link carrying the target URL and the spec itself, compressed into the link's fragment, so the spec never touches a server. A "Run all" link walks the whole set in sequence, an edit link reopens the set for revision, and one more link downloads it as a real .xlsx workbook for stakeholders who live in a spreadsheet. Anyone who opens a run link can run it: with Groma installed it runs in place, and without it the hosted run page handles it. A document has one base URL — the address its specs run against. Set it as you share (or while authoring, when you're exporting a session directly) and every link in the document is pointed there, so the same set can be sent out against staging one week and a review box the next by changing one field and sharing again. Only the server part of each URL moves; paths, steps and locators stay exactly as captured. Testers are never asked to pick a server. Report A completed run rolls up into a standalone HTML report with per-step verdicts and notes, a screenshot of every step that failed — and only those, so a picture in a report always means a failure — and a video of the run, sampled locally from the tab, so there is no screen-share prompt. A reviewer can watch it straight through skipping the pauses, or press "Play this step" on any step to see just that stretch. The report embeds the spec, so it's re-runnable: reopen it and go again. A failed step also carries what the app printed to its own console and the requests it made while the tester was on that step — method, URL, status and timing, never a body — so a developer reads the failure without having to ask for a reproduction. A "Run all" saves one archive instead: a contents page over a folder per spec. With a folder connected, each finished run is also filed into it, so every past run of a spec is listed on Home to reopen, download or delete. Why manual, not automated? Some things only a human can judge — visual polish, confusing copy, a flow that's technically correct but feels wrong. Groma isn't trying to replace Playwright or Cypress; it's built for the QA/PM pass those tools don't cover, and it can reuse the same data-testid your automated suite already relies on, so the two never drift apart. No package, no backend, no accounts. Groma is only a browser extension. There's nothing to install in your app, nothing to sign into, and no data leaves your browser except what you explicitly export or share.