Testing is a complex activity, involving many decision points and multiple possible approaches to the same end goal, that of ensuring the most useful information is provided about the tested software.
At the same time, nature is also complex, and an inspiration source for some very useful models, such as Cynefin. This sense making and context determining model is quite popular in the agile practices world, and can also be a good candidate for testing.
Is test automation the best approach? Should automation alternatives be considered? Should I build or buy my testing solution? These are some of the questions that people involved in testing are facing many times, and that can be made easier to answer to with the help of the Cynefin framework.
My session reveals how Cynefin can be used to make sense of the testing context, thus helping determining the most suitable approach for testing.
At the same time, since Cynefin is not a static model, the session highlights how the testing context is or can be changed, updating accordingly the testing approach.
- Awareness of the context challenges for testing
- Introduction of the Cynefin framework
- Mapping testing strategies to Cynefin complexity domains
- An example for supporting the “no-automation” decision