It takes three ingredients to maximize the impact of the software your teams makes, while maintaining a high quality:
- a whole team approach towards quality,
- the fastest feedback possible
- constant exploration
Our workshop is shaped around MBot, an awesome robot and it contains all of these ingredients. In small teams, participants will first discover how to control the robot, using Scratch (a visual programming language, programming experience not required.)
After some theory about the importance of a Whole Team Approach – and specification by example as a technique to boost this –, teams will work on examples of the intended behavior of the robot. In a few short iterations, the examples will be refined while we make our way towards re-writing the examples in the Gherkin language.
Of course, we will give lots of tips ‘n tricks to bring forward flaws in the product as early as possible, but we encourage participants to learn from each other.
Once the robot is ready, teams can hit our integrated test-track. This is where the real testing starts: teams can set up and perform experiments to learn from how the robot behaves. Observing the outcome of the experiments will give insights in how to improve the robot’s behavior.
The goal: lap the track as fast as possible, beating other teams to the finish. The winning team will be rewarded. Cheating is allowed.
Benieuwd naar de Agile Testing Days van vorig jaar? Lees dan de blog van Sander de Jonge waarin hij de drie meest interessante onderwerpen op het gebied van exploratory testing van de Agile Testing Days 2016 deelt.