HAVE YOU EVER DELIVERED A THEME, AN ARTICLE, A BOOK WITHOUT REREADING IT?
OR YOU HAVE EVER PRINTED IT AS IT WAS, HOPING THAT THE READER OR THE PROFESSOR WILL FIND YOUR ERRORS FOR YOU?
IF YOU REREAD IT: HOW OFTEN DO YOU DO IT?
Normally when you write something important, what you do: you wait to have written 300 pages to give a rereading? Or 50? Obviously the answer is the same for everyone: NO.
This is an example that I often give my clients about the theoretical and practical importance of software testing.
Writing software is like writing a book: especially when it comes to rereading it
Let’s take a student, a professional from another field, a journalist, a writer. We can take ourselves as an example, because in life, starting from school desks, we wrote something: when we reread what we wrote?
Well, depending on what we do when we write, without knowing it and even without ever writing a line of code in our life, we have already done a “test”: