From: Mike Jackson Date: Thu, 4 Apr 2013 14:11:41 +0000 (-0700) Subject: Added Verification and Validation X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=63f36a4ccb44a275740cb00fdfd9f3df6a8e2c8c;p=swc-testing-nose.git Added Verification and Validation W. Trevor King: I dropped the testing/Testing.ppt modification from the original 7bb33fb. Conflicts: testing/Testing.ppt --- diff --git a/testing/README.md b/testing/README.md index 606151f..2a3c847 100755 --- a/testing/README.md +++ b/testing/README.md @@ -24,7 +24,12 @@ Software testing is exercising and confirming expected behaviours and results fr * Our code can handle extreme boundaries of input domains, output ranges, parametric combinations or any other edge cases. * Our code's existing behaviour is still the same after we've changed it (this is called *regression testing*). -It also gives us the confidence to: +In testing, you'll come across the terms *verification* and *validation*, + +* Verification is the process of asking, "Have we built the software correctly?" That is, is the code bug free, precise, accurate, and repeatable? +* Validation is the process of asking, "Have we built the right software?" That is, is the code designed in such a way as to produce the answers we are interested in, data we want, etc. + +Testing also gives us the confidence to... * Add new features. * Optimise our code.