In my post on porting development lessons to testing I mentioned getting into the ideas of what makes the testing role something uniquely distinct from that of the development role. So let’s talk about this.
There’s often talk about how developers should think more like testers. But there’s often not as much discussion about the corollary: testers learning to think more like developers. So let’s talk about this.
I’ve talked about the notion of test description languages quite a bit. A lot of these discussions get into debates about being declarative versus imperative, or focusing on intent rather than implementation. All good things to consider. But such “versus” terminology tends to suggest there is a “right” and a “wrong” when often what you have is “What makes sense in your context.” And you may have to flexibly shift between different description levels. Let’s talk about this.
Recently I engaged in a fun exercise with a test team wherein each of us had to answer the following question: How do I describe my role? It’s always interesting to me to see how people answer this, particularly in the fields of testing and quality assurance. So here I’ll provide the answer I gave, along with a bit of context for it.
In this post I want to follow on a bit from the interactive exploration idea developed up to this point but also focus on the distinction of checking and testing that often gets debated. I also want to use this post to reinforce a few things I talked about last year.
This post follows on immediately from the last one, so let’s get started with the exploration!
Let’s continue our interactive exploration example. Here I’m going to provide a bit more of a complex scenario for you to consider. My hope is that you will take the time to engage with this idea, exploring the ideas around the central idea, and figure out how you would ultimately craft tests.
Let’s use this post to take stock of what I’ve done so far in the interactive series but also talk a bit about exploration as a core technique of testing, particularly around the idea of requirements.
This is the second post in the interactive exploratory testing series. The first post provided a relatively large amount of context as well as ending with a challenge. So let’s continue to explore this idea of exploratory testing with interactive fiction.
I want to start off 2017 by playing around with the idea of exploration. I gave an example of how I applied exploration while testing a particular game as well as creating a game to test the exploratory abilities of testers and even a little bit about reframing interviews with gamification in this context. I want to start taking this to the next level.