For teams with a new feature on staging and no tests for it yet.

Your setup

Say this to Certyn

We shipped bulk edit on /products to staging. Explore it for 30 minutes, file the bugs, and write test cases for what you verified, tagged bulk-edit.

If no test account is saved, opens the sign-in form (sign_in).
Says the run length and starts an explore run with your goal (app.run.create type explore, minutes 30). A run uses plan time while it runs.
In the run, Certyn reads the wiki, memory and past issues, then writes a checklist with the riskiest flows first: saves, deletes, access, pages full of data.
It tests each line. For each confirmed bug it first searches for a matching issue, then files a new one with screenshots, steps, expected and actual result.
Because you asked for test cases, it saves one for each real flow it ran and verified (app.testcase.create), with your tags. It updates a matching case instead of adding a duplicate.
It writes the run report: verdict, what it covered and what it did not.

One Certyn issue per bug, in review. Confirm or close each one.
Test cases tagged bulk-edit, with steps and expected results from what Certyn saw.
A run report with the areas it did not cover.
If you ask: a suite of the bulk-edit cases that runs after each deploy.

Test cases come only from flows Certyn ran and verified, not from every possible path. Read the "not covered" list and ask for a second run on those areas.
A test case gets the regression tag when you name no tags, so it joins the nightly Regression Suite.
Certyn judges against your request, the wiki and any spec. Without a spec, a missing feature is noted, not filed as a bug. Paste or attach the spec to get checks against it.
A feature behind a flag must be on for the test account.
A run has 60 minutes by default, up to 240.