You are here


Explicit Exploring Using Testopsies and Microheuristics

Prerequisite for attending the workshop: Attendees will need to bring their laptop.

In this workshop, you’ll learn more about what you’re doing when you’re doing exploratory testing. Through the exercises, you’ll gain understanding of:

  • Parallel threads and activities going on in your brain when you explore
  • How you make decisions what to do next based on what you’ve learned (microheuristics)
  • How to go about improving your own testing and teaching others about testing by using these techniques.

Exploratory testing is one of the key skills for the future. Come to this workshop to deepen your knowledge of it!

Better Estimation and Planning

When will it be done?

From the dawn of time, we're asking: How long will the project take, and when can we see something working. Especially in our Agile era when the market, technology and skills shift so quickly, we need to communicate estimates clearly and plan effectively, in a sea of uncertainty.

Over time, we've collected a few methods of estimation. We're going to discuss and experiment with them in this workshop, and taste what works and what doesn't. In addition, we're going to see what metrics we need to collect as we go, and how to interpret them to meaningful projection. Finally, we'll see if (and when) the NoEstimates method may be the right answer.

Topics covered in the workshop:

  • Why planning and estimation is important (and to whom)
  • Dealing with the uncertain and the unknown
  • Reducing risks in planning and reporting
  • Estimation methods (relative, story points, cumulative flow)
  • Pros and cons of the different methods
  • Estimating the unknown
  • Projection methods and meaning (Monte-Carlo simulations)
  • Getting real with NoEstimates


Key takeaways:

  • Why estimates suck
  • The priniciples behind using techniques like story points, velocity, flow, and principels planning poker that makes them effective (and what breaks them)
  • How to collect the right data to get better projection for the future
  • How to communicate effects effectively

Testing with Jest

Prerequisites for attending the workshop: Attendees will need to bring their laptop with the following setup done in advance:



Our front end is written in JavaScript & React, which is a JavaScript library for building user interfaces. Using Jest was an obvious testing choice for us, as Jest is an open source library used for testing JavaScript code & React applications. It requires zero configuration which meant testing sooner & delivering faster. Ideal for our microservices architecture. Jest is composed of many other packages like jest-snapshot, jest-validate etc, which makes Jest more than just a test runner with a built in assertion library. We used Jest Snapshot to test our UI components which works by taking a screenshot & compares it to a stored, reference image. The test fails if the two images do not match. We later realised that Jest Snapshot can be used for most JavaScript types including API responses, arrays, objects strings etc & not only UI components. If you are interested in learning more about Jest & Snapshot testing come join us.

Key takeaways:

  • Jest Snapshot testing
  • Component testing

How Video Games Can Inspire Creative Testing

In my 10+ years in QA, I have built my career on unconventional testing. But that all started with a love for video games and identifying bugs in software before I knew what a bug report was. Video games can play a crucial part in becoming a more creative tester, regardless of what industry you are in.  In this presentation, I hope to showcase how video games can create a new way of thinking when looking at everyday apps.  Gaming and testing are both passions of mine and I am excited to showcase how these can be used hand in hand. 

  • Why would video games be applicable to what I do?
    • ​Video games require a heavy amount of critical thinking and exploration.  Games like Assassin's Creed and Breath of the Wild encourage users to think for themselves and find their own path.  This, in turn, induces immense creativity in finding new ways to explore.  For me, this helped me find bugs I never would have thought to look for.  My time in Assassin's Creed 3 sailing around the vast ocean in a ship helped me find one of my first "out of the box" bugs at Disney where I sailed on a boat and found a hole in the map after 2.5 hours of sailing. 
    • Additionally, some video games, such as Dark Souls and Bloodborne are linear but have an elevated difficulty.  Users have to learn constantly as they are defeated by the same enemies, causing them to rethink their strategy and get creative. 
  • Speak more to my experience of this, including examples of what I have been able to find using my gaming experience.  (Will flesh this out heavily for presentation submission)
  • Hands on practical learning via examples provided 
    • Activity 1: I will have game capture footage of an open world game (Breath of the Wild) and one linear game (Bloodborne) to show.  This will showcase points from the above regarding the need to explore or learn from mistakes.  I will prompt the audience to identify ways these scenarios that can help them build what they are currently doing in their day to day testing. 
    • Activity 2: QA a mobile app - Using the knowledge from Activity 1, I will display a mobile app (Super Mario Run) and prompt the audience to give ideas on how to find more creative ways to find a bug in the app. 
  • Both activities above will require audience participation. I will bring an Apple TV for airplay purposes. 
  • Questions


Key takeaways:

  • Learn how video games can provide a great creative outlook to taking the step in becoming an exceptional tester.

  • Participants will be able to challenge their normal testing process to rejuvenate their testing outlook.

  • Using the info provided, a new competitive edge for testing employment is introduced with the addition of critical and creative thinking skills.

  • Participants can use this knowledge in their every day lives, which may help them troubleshoot non-testing issues! 

Improving Testing Through Operability

Sold out

Reliability, handling failure gracefully and recovering quickly are becoming increasingly important as the software development world adopts DevOps culture and practices. Outages and security failures are big news and many companies are investing heavily to avoid these challenges. Operable systems are easy to deploy and test, provide actionable information about their state and behave more predictably in adverse conditions.

Testers on development teams are often used to testing changes to the functionality of an application but less so testing how operable a system is. My recent experience has seen testers on teams charged with improving operability for systems through better logging, monitoring and system control measures (such as feature flags) to emit better information. This information on system stability and state is critical to testing and we can influence its creation profoundly.   

Why it is important for testers

  • As the operability of systems becomes a greater focus, testers need to be equipped with models to think about how to add value in this context.
  • As testers, we strive to add value and testing for reliability enables us to use our risk analysis skills to explore for failures and how to recover.
  • If we get involved with helping our system to emit better information from an operability standpoint, testability through observability and control will likely be enhanced.
  • Rather than having shallow status checks, testers can contribute to meaningful monitoring of customer journeys and how reliability and recovery are measured.


Key takeaways:

  • Recognise the key terminology pertaining to logging, monitoring and system control measures and their role in operability.
  • Understand how to test systems for the quality of operational information that they emit and how this can help improve information gained through testing.
  • Apply the understanding of operational insights to improve testing of functionality and system control measures (such as healthcheck, config change, system status change endpoints and feature flagging) to enhance overall operability.
Subscribe to Terrassisaal