A screenshot of a checkout error can get everyone’s attention. It’s what happens a day later that interests me. The developer has changed something and wants to know if it works. The person who first saw the error has signed off for the day. Can someone else open the report, repeat the same order, and tell the difference between a fix and a lucky attempt?
Give the next tester a starting place
For an example, suppose a test customer can add two units of an item when only one is available. “Checkout is broken” sends the developer hunting through payment, shipping and account settings. A report that starts with one available unit, two in the basket, and a specific test order gives them somewhere to look. Include the build or test environment so they know where the observation belongs.
I’d capture the customer view and the staff view together. The customer might see a confirmation while the order list stays empty. Or a staff order might appear even though the customer sees an error. An image of either screen by itself leaves the reader guessing which part of the transaction happened. Use a test account and crop out any unrelated customer details.
Say what you actually observed
I like a report that keeps one sentence for the observation and another for the expected result. In this example, “The customer received a confirmation for two units” records what happened. “Accept no more than the one available unit” gives the team a decision to check. Whether stock should be reserved in the basket or at payment is a product question the team may still need to settle.
That distinction keeps a diagnosis from hardening into a fact. The tester can tell us that refreshing the staff page made the order appear. The developer can investigate why the first view was empty. Both pieces of information matter.
Close it with a second attempt
After the change, I’d run the original order and then try buying the single unit that really is available. Rejecting every order would make the first test look good and put the shop out of business. The second attempt checks whether an ordinary customer can still buy something. A short recording of both attempts, with the staff order and stock count visible, is the report I want to get back.


