Story type: Testy Tips

Ask what else uses the component before agreeing the regression scope. A one-line change to a shared date picker can affect forty screens, three countries and every user born in February.

Check the response body as well as the status code. A 200 OK can still contain a beautifully formatted explanation of how everything has failed.

Clear cookies, reset the account and record every step. “Click around until it breaks again” is exploratory testing’s drunk cousin.

Check roles, account status, dates, balances and previous transactions before raising the defect. Sometimes the application is broken. Sometimes Dave has been configured as a deceased administrator living in 2047.

When a developer says it works on their machine, ask whether they plan to let the customers use their machine as well.

Put the build number in every defect, screenshot, log and video. “Works for me” becomes much less impressive when they are testing build 84 and you were given build 81.