Skip to content
certyn logoCertyn
Start Free
RecipesDoc

Customer Complaint to Issue, Code Pointer and Regression Test PR

Certyn reproduces a complaint with evidence, files the issue, finds the code involved in your repo, and opens a pull request with a regression test.

For teams who want each customer complaint to end as a test, so the bug cannot come back unseen.

Your setup

  • A complaint in plain words, for example from support.
  • The app on staging, with a test account.
  • The app's code and tests in a GitHub repo. You review changes as pull requests.

Say this to Certyn

Customers say their discount disappears when they change their address at checkout. Reproduce it on staging, file it, find the code in acme/shop, and open a PR with a regression test.

What Certyn does

  1. Searches for a matching issue (app.find) and shows it if one exists.
  2. Says the run length and starts a short explore run with the complaint as its goal (app.run.create type explore).
  3. If the bug reproduces, the run files a Certyn issue with steps, expected and actual result, and screenshots.
  4. If there is no GH_TOKEN yet, opens a form for it: a fine-grained token for that repo, Contents and Pull requests Read and write.
  5. Clones the repo on its Machine and searches the address and discount code. It adds the suspect files and lines to the issue (app.issue.update) as a lead, not a proven cause.
  6. Writes a regression test in your framework and style on a certyn/<name> branch, and runs it against staging. It must fail now, for the same reason the run saw.
  7. Opens a pull request that links the issue and says the test fails until the bug is fixed.

What you get

  • One Certyn issue with screenshots and the suspect code.
  • One pull request with a regression test that shows the bug.
  • After the fix ships: say retest issue 31. Retest needs the issue confirmed and linked to a tracker issue or a test case.

Limits

  • An issue filed from the chat itself holds text only. Screenshots come from the run, not from the chat's Machine.
  • The test fails until the fix is merged. Merge both together, or ask Certyn to open the PR against the fix branch.
  • Certyn points to code; it does not change product code here. For a fix PR, see Send a Confirmed Bug to GitHub Copilot.
  • Certyn uses your test account, never the customer's. Name the plan, coupon and countries in the request.
  • Certyn never merges.
PreviousUse Certyn's REST API from Your Own ScriptsNextCheck Your Getting-Started Guide and API Docs by Running Every Example