Hi James
You are right, self-testing-software more than just unit testing. It's an approach and a mindset.
At a very simple level if we ever find a bug, we write an automated test to expose that bug, that way it can never come back silently.
You are building, what Steve Maguire in "Writing Solid Code" called "The Hypothetical Compiler" in which he asked the question, "What if we could extend the compiler to catch more than just syntax bugs for us?"
You might get some value out of an article I just wrote for Developer Fusion about testing in an agile world.
http://www.developerfusion.com/article/136381/testing-in-an-agile-world-the-heart-of-a-developer/
Good Luck
Malcolm
Hi,
question for my esteemed colleagues:
Continuous deployment / continuous delivery is a hot topic these days. And one area I'm particularly interested in is 'self-testing software'.
What are people's opinions on what is meant by 'self-testing software'? What does this look like? Is it unit testing by another name? Or is it deeper than that? Does it include the automation of black box tests? And is this now done by the developers? (I'm in a traditional developer / tester agile'ish team).
Thanks
--
Malcolm Anderson
Scrum Coach & Agile Engineer
http://www.PragmaticAgility.com/blog
0 comments:
Post a Comment