After being a tester for half a decade, I have found that learning and discussing the ideas and practices that interest me can only do so much for my continued professional growth. While being able to understand concepts, practices or tools is a good starting point, it takes constant deliberate practice to actually be able to explain those things to others in a coherent manner.
So after years of neglecting to write about the things that I am doing, I decided to try again. This time, I have a good amount of peer pressure to help me start and then keep on going. Special thanks to Carol Brands who published her first blog post before I did!
Since it took me a while to catch up with Carol, I have had time to contemplate what I want to write about and share with other testers in the world. My mission statement is as follows:
This website is will become a resource for technical testing that follows the Context-Driven Testing paradigm.
Context-Driven Testing simply means that I agree with the seven basic principles of the Context-Driven School and will attempt to follow these principles in future posts.
The term technical testing is not as easy: The CDT paradigm demands an answer to the question “technical to whom”. I confess that I cannot describe “technical testing” with any certainty, but I doubt there is any widespread agreement on the matter to begin with. However, I claim that there are skills that might be considered technical and from which most testers can benefit. I will attempt to write about those skills here.
The goal is to write about skills, concepts, practices and tools, how testers can potentially benefit from them and in which contexts they might have a high impact or instead provide little to no value at all.
Or simply….putting technical testing stuff into context.