The current date was not shown, mouse clicks, or taps were not visible, and the sound was recorded... Yes, testers make some common mistakes while creating an attachment, and in this article, we will present the most common mistakes in attachments, so let's start.
Desktop recordings
The mouse icon and mouse click effect are not visible in the recording.
The current date and time are not visible.
The URL field is not visible in the screencast.
Low attachment resolution.
Time is not in 24-hour clock or AM/PM format if the tester uses a 12-hour clock.
Mobile recordings
Taps/touches are not visible on Android devices.
Screencast has a low frame rate.
Common mistakes Desktop/Mobile recordings
Sound is recorded.
A screencast is more than 60 seconds for the bug report and more than 15 seconds for Bug Reproduction and User Story executions.
The current date is presented in another language than English (or optional German).
The screencast shows more than the basic required steps.
Common mistakes Streaming device recordings
The screencast resolution is Low.
The ambient light is too dark.
The Remote Control is not fully and clearly visible.
A screencast is more than 60 seconds for the Bug Report and more than 15 seconds for Bug Reproduction and User Story executions.
Screenshots
The bug is not highlighted on the screenshot.
The second screenshot, containing the current date and time, is not added to the bug report when submitting a bug via a mobile device.
All these examples above are testers' most common mistakes while creating an attachment. We'd like to remind you again to read our Bug Report Attachments article to learn our attachment requirements properly.
Now, we will show you what an attachment (screencast and screenshot) should look like.
Let's start first with the screencast. Imagine that the bug occurs in the following steps:
Title: There is no reaction after the user clicks the "Become A Tester" button on the Become a Tester page
Open https://test.io/
Click on Global (EN) at the header and change the language to DE
Click on Crowdtesting in Navigation
Scroll down Erfahren Sie mehr über Test IO and click on hier link
Click on the " Become A Tester button under the Join Our Freelance Testing Community heading
A proper screencast for this bug will look like this:
As you can see, the screencast contains all the requirements we have for it and also shows only the basic required steps: the last navigational step, the action that triggers the bug, and the bug itself. In most cases, you do not need more than 10-15 seconds for a screencast, and you can achieve this quickly by recording only the last navigational step, which will trigger the bug and the bug itself.
Now, let's see what a proper screenshot should look like. Imagine that the bug occurs in the following steps:
Title: "Become a Tester" button under the "Join Our Freelance Testing Community" heading is only half visible on Become a Tester page.
Open https://test.io/
Click on Become a Tester in Header
A proper screenshot should look like this:
As you can see, the whole screen is captured, the URL, current date, and time are visible in the attachment, and most importantly, the bug is highlighted.
We hope your skills in creating attachments will go Up after reading this article, and we hope you will make even better attachments.