Date: Sunday 19th June 2016
Time: 3.30pm – 5.30pm BST (click here to check your local time)
Facilitator: Neil Studd
Attendees: Trisha Agarwal, Dan Billing, Christian Kram, Zoltán Molnár, Kapil Saxena, Adina Sit, Dolores Zurdo
With football fever taking hold of Europe, this month’s Weekend Testing Europe session followed the Euro 2016 theme. We staged a two-part exercise to analyse and investigate the official Euro 2016 website.
Firstly, we performed a product recon to establish the purpose of the Euro 2016 website, its features and its potential audience(s). Zoltán Molnár made an astute observation that I had asked people to classify the “major” and “minor” features of the site, but I hadn’t provided any sort of clarification as to what those terms meant. Make sure your requirements are clear, to avoid making false assumptions!
Both Christian Kram and Dan Billing presented the results of their recon in the form of mind-maps, providing structured answers to all of the questions I’d asked. Their responses had the makings of a Product Coverage Outline, something we’ll be covering in a forthcoming session.
As part of gaining familiarity with the site, several people reported stumbling across issues or oddities. Christian managed to crash his browse; Dolores Zurdo observed issues with the video player, which were also experienced by today’s facilitator Neil Studd.
After reviewing the results of this recon, the group had a much firmer understanding of the site’s content and purpose. Using this information, we proceeded into a half-hour bug bash session, using the information we’d gathered to guide our search for potential problems.
Despite the short amount of time to look for bugs, we uncovered several interesting issues. The video player, in particular, seemed full of issues: Neil used a site spidering technique to demonstrate a large volume of HTTP 404 errors, and Dolores refined her earlier investigation to produce some replicable screen corruption:
— WeekendTest Europe (@europetesters) June 19, 2016
You can read more details about the steps to reproduce the bugs that we found, by reading the session transcript below.
All in all, it was an action-packed session – we don’t normally try to cram two separate practical sessions and debriefs into a single afternoon, but we reaped rewards with the issues that we found!
Follow us on Twitter for more session updates.