Turn a customer report into a proven fix: reproduce it, find the cause, fix it with a regression test, prove it in a browser and push it for review.

On this page

This guide takes a customer’s bug report to a fix that is reproduced, tested and proven in a browser, pushed on a branch for review; the example is “The Pay button does nothing on Safari.” Before you start, you need a Code thread in the desktop app or the CLI on the repository’s folder, and whatever the customer sent (a screenshot, an error log).

Steps#

Write the brief, asking for proof#

Put in what you know, and ask for a reproduction, a regression test and browser proof. The bug is about something a person clicks, so without browser proof the criterion would be reported unproved.

Brief
Fix the checkout drop-off: the Pay button does nothing on Safari.
Reproduce it first. Find the cause, fix it with the smallest change, and
add a regression test. Prove the checkout works in a browser at desktop
and mobile widths. Don't change the payment provider integration.

Attach the evidence#

Add the customer’s screenshot or error log to the message, then send.

Answer if it can’t reproduce#

Ysra finds your project’s commands and reproduces the problem before changing anything. If it can’t, the task goes to Needs your input: add the missing condition (“only when the cart has a discount code”).

Read the result#

In the review pane’s Report and Changes tabs (see Review the diff):

Look at What a good result shows
Repository checks The regression test and your suite passed on this exact change
Acceptance Pay works on Safari is proven by an executed browser run
Changes A small diff that touches only the cart

Commit and push#

Commit the fix on a new branch and push it; pushing asks first. See Commit and push.

The fix is on a branch for review, and your repository’s CI result comes back into the thread.

If it doesn’t work#

Symptom Why What to do
Ysra can’t reproduce the bug It asks rather than guess a fix. Add the missing condition: browser version, account state, data.
An unrelated test fails It was failing before the task started. Nothing: it is reported as pre-existing and doesn’t block the fix.
The browser criterion is unproved The browser couldn’t reach the app (a port, a sign-in, a service). Tell Ysra what the app needs to start; the environment is fixed, not the code.
Didn't work after repairs Checks still failed after Ysra’s repair attempts. Read the reason, then steer and Continue.
YsraDocs