User Stories Attachments
User stories are an excellent way to get to grips with a customer’s product and start earning as a Test IO tester. If we want to hit our standards, we’ve got to follow these rules when making attachments.
❝
New attachments have to be created for every bug report or reproduction.It is prohibited to copy attachments from other bug reports or reproductions.Attachments must show all relevant bug information to serve as proof.All relevant information must be displayed in English (or optional German if the bug report language is German), e.g. the date, time system information, and error messages.You should select only one device or browser when you are reporting the bug, and upload only attachment for it. If you are able to reproduce the bug in other devices or browsers, please mention this in your Actual result.Don’t show any information about other Test IO customers that can be related to Test IO (e.g. invitation emails or browser tab names). Showing installed apps of other customers is permitted.Don't show any personal information or unprofessional data such as pictures, videos or autocorrect bad word suggestions. Remember your attachments will be available to other testers, to the test IO staff and to the customer so be careful with what you're showing on them.For website tests, the URL field must be visible on attachments.The resolution must be high enough so that the text and elements can be easily identified.Please always record your whole screen.A crash log is mandatory for bug reports and positive reproductions of app crashes. The video that documents the crash has to correspond to the attached crash log, i.e. timings must be coherent❞.
Take a minute to check out this screencast, following the above rules.
Does it meet our standards?
It’s super helpful to review the work of other testers, as it helps us learn. When we see any mistakes, it sticks in our brain and reminds us to avoid them next time.
Everything seems good, right? But, do you remember this important thing:
❝For website tests, the URL field must be visible on attachments.❞
On this screencast, the URL cannot be seen, which is crucial information about the location of the behaviour reported.
The URL is important because it tells you where the behaviour happened. This is true for all attachments, and for User Stories, it’s even more crucial to ensure that the execution matches what you intended to test.
💡 Always double-check your attachments, especially for User Stories, because they can’t be changed once submitted!
Hey, Coppers!
If you’re unfamiliar with our new Tester Levels system, now is the time to learn more. Discover what it takes to reach the Diamond level and the benefits of each level.
Reminder of the week!
Just a heads up from our Academy article ❝User Story Review & Payout❞: don’t forget this important point!
💡 If your work gets rejected, talk to your team lead and ask them over the Test Chat to give you more detailed feedback on why it’s not up to par. This way, you’ll be able to improve and avoid getting kicked out of testing user stories.