ExpoQA 2022 was a conference that took place in Madrid between the 31st May and 2nd June 2022. This week I will be posting some sketchnotes for the talks that I attended.
It is tough to get developers interested in testing. Inspired by Mob Programming, Andrea decided to experiment with Mob Testing (or Ensemble Testing) where the whole team is involved in testing a feature or application. It is something I’ve tried out in the past, especially when testing features which are high risk. Andrea suggested that this exercise can also be good for knowledge sharing, and learning more about a feature which some may be unfamiliar with. This has inspired me to give Ensemble Testing (which is a much nicer name than Mob Testing) another go.
- Encouraging developers to take part in testing can be a challenge.
- Mob Programming is a process where multiple developers work together to complete some programming. The roles taken by developers in a mob programming session are:
- Navigator – who guides the session
- Driver – who works at the computer, typing out the code as suggestions are made
- Spectators – who observe the session and offer suggestions
- The process of mob programming can easily be applied to testing. A mob/ensemble testing session follows a similar format to mob programming, but instead of programming the team is testing.
- The aim of an ensemble testing session isn’t just to find bugs, but can also be to share knowledge and help the team understand how different features work.
- Benefits of ensemble testing include:
- Improved go-live confidence
- More collaborative team culture with more discussions and conversations about the features.
- Improved knowledge of the application and features across the teams