#21 Greenhorn 💚 Newsletter

User stories key attachments specification | Linking bugs to User Stories drop-down | Reminder of the Week: Missing Images

Charlie avatar
Written by Charlie
Updated over a week ago

User Stories Bug Linking

User Stories have a way to link bugs when you cannot confirm, or you're blocked when executing them because you cannot reach the right feature area that, even if it is optional, should be used so customers understand the User Story execution and the bug better.

Image of the linking bug drop-down location and button to submit a bug.

Remember, If there is no bug reported yet or you couldn't find it on the ❝Known Bugs❞ list, we recommend you submit a new bug first and then finish the User Story execution.

ADVICE: Check the Known Bugs list for each feature within the scope to save time when identifying duplicates manually.

User Stories Attachments

Attachments such as screencasts and screenshots serve a crucial purpose in bug reports as well as user stories. They provide visual evidence and additional context to help customers understand and reproduce the issue being reported.

Here's how these attachments contribute to the bug-reporting process:

  1. Visual evidence: Screenshots and screencasts allow developers to see the bug or issue you're encountering firsthand. Visual evidence helps them quickly grasp the problem and understand its impact on the application or system.

  2. Reproducibility: Detailed steps to reproduce a bug are essential, but sometimes they may not capture the exact scenario or context in which the issue occurs. By including screenshots or screencasts, you provide developers with additional information to help them recreate the bug accurately.

  3. Clarity: Attachments help eliminate any ambiguity or confusion that may arise when describing a bug in text. They offer a clear visual representation of the problem, making it easier for developers to identify and comprehend the issue found.

  4. Efficiency: Visual evidence allows developers to quickly assess whether the reported issue is a bug, a configuration problem, or a misunderstanding. This saves time and enables them to prioritise and address bugs more effectively.

Additionally, ensure that the attachments of user stories are of sufficient quality and resolution, so the development team can easily view and understand them and always follow our rules:

Avoid submissions like the following ones:

Here's a real example of how 5 user stories were executed with 12 attachments instead of the expected 5.

REMINDER: Only one screencast must be attached to the user stories and cannot be used for other purposes, like documenting a bug or other user stories.

The reminder of the week!

Missing and placeholder images are tricky when starting with manual exploratory testing; however, they are very easy to spot!

While broken images fail to load or display correctly on a website, you may see an error icon, a blank space, or a broken image symbol instead of the intended image.

On the other hand, placeholder images are intentionally used as temporary visual representations until the actual images are available; visual cues indicate that no specific images will be displayed. Unlike broken images, placeholder images are not considered defects as they serve a temporary purpose.

Find out all about it in our Academy article ❝Content Bugs❞, section ❝Understanding Broken Images and Placeholder Images: A Guide for New Testers❞.

What is the reason for the image above, and how is it caused? Is it a missing or a placeholder image?

TIP: This image will be displayed regardless of the browser used.

Did this answer your question?