When it comes to software testing, it is essential to include a summary of how user stories were executed to ensure clear communication and proper documentation.

This comment serves as a concise overview of the testing process, capturing the main steps undertaken to validate the software’s functionality. By highlighting the key actions and outcomes in just 2-3 sentences, the summary comment becomes an invaluable resource for stakeholders to quickly grasp the testing approach and results.

Like Aziz Amreliwala and linaohanessian did in the following user stories:

Excellent job, team!

As a reminder, here is the information your User Stories comments must provide:

TIP: A helpful tip for providing feedback is to include the inputs you used and the names of the elements you interacted with on the website, similar to how you would include this information in a bug report.

Attachments containing visual information are crucial in assessing how end users perceive websites.

This is the reason for having as General attachment requirements the following:

This week, let’s focus on being attentive to the relevant details that should be included in a bug report attachment. Specifically, ensure to capture the website being viewed on the current viewport.

TL André (andre-47) would like to advise everyone to refrain from uploading attachments like the one provided when documenting bug reports, bug reproductions, and user stories.

Here is an example of a screenshot that captures the entire webpage on a mobile device, but not the current device’s viewport.

The attachment is a portrait Mobile screenshot of the entire web page! Please note that this may not accurately reflect the user experience when accessing the website on a mobile device.

Our TL also wants to remind us: ❝Generally, for screenshot always a proper snippet of the screen should be chosen where everything is clearly visible: The website with the bug marked, the current date and the browser address line. The last one especially is also important on screenshots from mobile devices. Often the address line is hidden there. But it needs to be visible to ensure the tester tested on the correct domain.❞

ADVICE: When testing a website that falls within our scope, we should treat it like any other website we browse online. Adopting an end-user perspective is crucial for achieving success.