While supplies last! Free 2022 Essentials of Interventional Radiology Coding book with every ICD10monitor webcast order. No code required. Order now >

We hear the term “testing” on a daily basis and see hundreds of articles on how important testing is, and yet these warnings often go largely ignored. This results in installing defective software and business processes into production. Why does this happen, time and time again?

For the most part, it is a matter of competing priorities in addition to the simple fact that there never seems to be enough time or money to do it right. The key lesson to learn here is that if you don’t have time to do it right the first time, by default you must have time to do it over again. We’ll touch upon this recurring theme again, because you can’t skip testing – you can only put it off until later, when it costs many times more to fix the problem.

Unit tests, system tests, integration tests, smoke tests, whitebox, blackbox, load, stress, user acceptance testing, end-to-end testing: we can tend to use these testing terms interchangeably, as if everyone understands what their true definitions mean and what specific tasks are supposed to be completed during each test phase.


You May Also Like

Leave a Reply

Your Name(Required)
Your Email(Required)