At Test IO we perform exploratory testing: ❝(...) a software testing technique in which the tester actively explores the application to identify defects, gain an understanding of the software and determine how it should be tested.❞

So the goal of exploratory testing is to find defects; to do so, we need to be creative and think outside the box.

Like detecting that adding a product to the ❝Wishlist❞ before and upon registration is swapping the items that are pushed to the functionality to be saved:

Analysis: A user started adding the ❝BRADLEY YAMASKA hoodie❞ to the Wishlist, prompting it to the Registration process since he hasn’t an account yet. After the registration process, he navigated to a different product: ❝SLIPPER GREY – KINSEY❞ and tapped on ❝Add to Wishlist❞ for this product; however, the adding to the wish list confirmation message told incorrectly that the hoodie product had been saved instead of the slippers.

This report also shows a clear understanding of our reporting standards.

Good job, priyalmultani2101!

When testing, use your intuition to identify user flows that require additional testing, and keep exploring until you are confident that all possible paths users might take are covered!

Another excellent example of thinking outside the box is this bug on a ❝Wishlist❞ feature.

Analysis: In this case, the user removes an item from the bottom and tries to update the following item's size; however, the system automatically removes the user's selection.

Good job, sgofl18!

The execution on the screencast is also excellent. Notice that no extra scrollings, clicks or movements introduce noise to the video instead of clarifying the behaviour.

When testing, always remember the user experience to ensure the software is intuitive, easy to use, and meets customer expectations so you can evaluate bugs better.