There’s no denying it. Testing is awesome and the most fun and amazing part of any product development!
Strangely enough, I have found that most people look at me weird when I exclaim something like this. I don’t know why…
I’ve often been the first tester in a project. A very common first reaction from colleagues is that test is not performed at all in their team, but I don’t believe that’s the case. Just because your team doesn’t have a dedicated tester it doesn’t mean you don’t test! Where there are professionals, there is a lot of quality work being done. Some of it is just second nature to all of you. Let me list some examples!
For many tasks, test data is required from the get-go. Oftentimes the developers fix this without regarding it as a test activity.
Code review is increasingly becoming a standard practice. Code reviews have so many benefits it’s hard to count. One of them is that they increase quality, and thus this is a test activity.
Before release, the new deliverable is shown to the customer. This acceptance test is a test activity.
At the start of a project, it’s unlikely that we will have all the requirements in place. Refining requirements to match new findings is a – you guessed it – test activity.
I believe we all have experienced UX flows that didn’t quite communicate the intended message. Tweaking the UX flow as we go is a test activity.
Development environments usually don’t look and feel the same way as a production environment. Making sure that what works on my machine also works on your machine, is a test activity.
There you have it – a small selection of quality work that is already in place in many ongoing projects.
I’m trying to make the case that everyone in a team performs test activities. However, everyone needs to feel confident that what they’re doing is the right thing… that their quality work has quality. There is always room for increasing your confidence in the product, and that’s where a dedicated tester excels.
So tell me – who’s testing in your team?