Please note: this post was originally written for BJSS’s internal blogosphere. If you find this interpretation of what role testers play in the delivery of software appealing then please get in touch as we may have a job waiting for you.
Recently, I commiserated with a developer on missed opportunities in past projects. This was a great chance to spitball ideas for test and assurance design. What follows is a bit biased towards righting old wrongs, but may be good enough to revisit for future projects. Anyway, this is what I came up with:
Welcome to another blog post! As usual, these are my opinions. Not facts. Disagree with anything I’ve said? Get in touch, let’s talk. Happy to have my mind changed. Having said that…
Today I have been thinking about why I prefer the phrase “good practices” over “best practices” in test design. My preference is so tenacious that I exchange the word “best” for “good” when the topic comes up, as if I’m trying to change people’s minds in a subliminal way. But why?