Boundary Value Testing

Team. We found a couple of weblogs which discuss different issues in software testing. They are at:

http://writingtestcases.blogspot.com/2013/07/boundary-value-analysis-example.html

and

http://blog.sei.cmu.edu/post.cfm/common-testing-problems-pitfalls-to-prevent-and-mitigate

The first entry discusses boundary value testing. For most of our test cases, we will test three conditions based on the return value from the stencil tag handler. This value can be a null, empty, or arbitrary length alphanumeric string. So our our boundary condition is based on string length: (null, 0-length, and greater than 0); Remember we are not testing the functionality of a complete web application; we are only assuring the quality of the generic controller for creating these type of systems. As a result, the testing will not be as involved.

There are some interesting fact in the second weblog which quantify the cost of software testing failures each year in the United States economy alone.

We will have more for you on Friday. La-La.