Testers on the other-hand [some would argue] are more like scientists. They don’t build anything (other than tools and frameworks, used to perform their science), instead they start with a proposition. Often that proposition comes in the form of “this piece of software works” and testers work to either validate that claim, orrrr take a sledge hammer to the claim to demonstrate that it categorically doesn’t work as suggested.
It’s an interesting differentiation and is something I only became aware of because a tester who used to be a developer posed the idea to me. It really got me thinking, because Art and Science are both, frankly, awesome. They’re both also very different.
Some of you might have seen a speech delivered by Tim Michin (full speech here), an Australian comedian who spent a portion of his life in the UK. He makes a point that art and science is at odds with one another, he references the Australian PM at the time not believing in climate change because he’s religious. He explains that artists and scientists need to do a better job of communicating to overcome their differences and achieve their goals. Now that I have another perspective – that understanding the differences between Developers [Artists] and Testers [Scientists] – I can’t help but think this a very similar point to the one raised by dev teams and testers time and again, communication is key. You hear about it at countless conferences, events, meetups, talks, online discussions etc. etc.