c# generating barcode Case 12 Test Description A group of 10 employees, each of whom has a salary of $0.00. in C#

Creation European Article Number 13 in C# Case 12 Test Description A group of 10 employees, each of whom has a salary of $0.00.

Aside from guessing that errors show up around boundary conditions, you can guess about and test for several other classes of bad data. Typical bad-data test cases include Too little data (or no data) Too much data The wrong kind of data (invalid data) The wrong size of data Uninitialized data

Some of the test cases you would think of if you followed these suggestions have already been covered. For example, too little data is covered by Cases 2 and 12, and it s hard to come up with anything for wrong size of data. Classes of bad data nonetheless gives rise to a few more cases:

Case 13 Test Description An array of 100,000,000 employees. Tests for too much data. Of course, how much is too much would vary from system to system, but for the sake of the example assume that this is far too much. A negative salary. Wrong kind of data. A negative number of employees. Wrong kind of data.

14 15

When you try to find errors in a program, it s easy to overlook the fact that the nominal case might contain an error. Usually the nominal cases described in the basis-testing section represent one kind of good data. Here are other kinds of good data that are worth checking: Nominal cases middle-of-the-road, expected values Minimum normal configuration Maximum normal configuration Compatibility with old data

Checking each of these kinds of data can reveal errors, depending on the item being tested. The minimum normal configuration is useful for testing not just one item, but a group of items. It s similar in spirit to the boundary condition of many minimal values, but it s different in that it creates the set of minimum values out of the set

of what is normally expected. One example would be to save an empty spreadsheet when testing a spreadsheet. For testing a word processor, it would be saving an empty document. In the case of the running example, testing the minimum normal configuration would add the following test case:

The maximum normal configuration is the opposite of the minimum. It s similar in spirit to boundary testing, but again, it creates a set of maximum values out of the set of expected values. An example of this would be saving a spreadsheet that s as large as the maximum spreadsheet size advertised on the product s packaging. Or printing the maximum-size spreadsheet. For a word processor, it would be saving a document of the largest recommended size. In the case of the running example, testing the maximum normal configuration depends on the maximum normal number of employees. Assuming it s 500, you would add the following test case:

The last kind of normal data testing, testing for compatibility with old data, comes into play when the program or routine is a replacement for an older program or routine. The new routine should produce the same results with old data that the old routine did, except in cases in which the old routine was defective. This kind of continuity between versions is the basis for regression testing, the purpose of which is to ensure that corrections and enhancements maintain previous levels of quality without backsliding. In the case of the running example, the compatibility criterion wouldn t add any test cases.

Let s suppose you re writing a test case for a nominal salary; you need a nominal salary, and the way you get one is to type in whatever numbers your hands land on. I ll try it: 1239078382346 OK. That s a pretty high salary, a little over a trillion dollars, in fact, but if I trim it so that it s somewhat realistic, I get $90,783.82. Now, further suppose that this test case succeeds, that is, it finds an error. How do you know that it s found an error Well, presumably, you know what the answer is and what it should be because you calculated the correct answer by