11. The Situation Many test cases are influenced by multiple test parameters, each with several significantly different inputs (or equivalence classes). Typical problem arises when they have to be executed covering all possibilities/combinations.
12. An Example Think that a registration page has to be tested which has four fields- Username, Password, E-mail, Receive_notifcations. Let us say that Username can have two types of valid classes on inputs and three classes of invalid inputs. Similarly let us say that Password can have four valid classes three invalid classes of inputs. E-mail, let us say, can have four valid classes and two invalid classes on inputs. Receive_notifications can be Yes or No. Let us say that all these fields have to be tested in three browsers IE6, IE7 and FF3. Here we are talking about each input having some significance in the system behavior. To summarize, following is what we are looking at as the Test Parameters that drive the registration tests. Username: Valid1 , Valid2 , Invalid1 , Invalid2 , Invalid3 Password: Valid1 , Valid2 , Valid3 , Valid4 , Invalid1 , Invalid2 , Invalid3 E-mail: Valid1 , Valid2 , Valid3 , Valid4 , Invalid1 , Invalid2 Browsers: IE6 , IE7 , FF3 Receive_notifications: Yes , No If we were to test all the combinations of values of the above Test Parameters, we are talking about 5 * 7 * 6 * 3 * 2 = 1260 ways to configure test inputs. There is a clear need to reduce this number without compromising Test Coverage.
13. Benefit from TestersDesk.com Welcome to Pairwise Testing (if you are not already enjoying its virtues). We generate a very reduced number of Test Cases that cover all the two-way interactions between all the values of all the test parameters. Each value of each test parameter talks to each value of all other parameters at least once. Now, that's intelligent test design. The list produced by our tool, and the additional tests identified by your judgment/experience yield the maximum number of defects in the shortest possible time. For the example presented in the previous slide, we provide as little as 42 Test Cases that guarantee Pairwise Coverage. Check it out!
37. An Example There are three fields on a screen each of which take a numeric range. Each individual field has been tested with the seven tuples (values) viz. min-1, min, min+1, mid, max-1, max and max+1. The expected behavior was achieved, however there is no guarantee that the "interactions" between the seven tuples of all the fields together work as expected. What if there is an error that surfaces only when the min+1 value of field #1 and max - 1 of field #2 occur together in a single test - does our test suite has test cases to catch such defects?
38.
39. Boundary TestCase Generator (BVA++) multi-field boundary value analysis tests can be generated Value to Software Testers
42. An Example Let us say that a banking application works perfectly in showing the balance money when the test actions are done in the following sequence- Change Password-->Check Balance--->Transfer Funds Let us hypothetically say there is a conflict on the data updating process when balance is checked after changing the password, then the following sequence may not work- Transfer Funds--->Change Password-->Check Balance
61. The Situation The Application Under Test takes a file as test input. This file has several fields in a specified format. There is a need to prepare multiple files each having different test data. In the end you have, let us say, a large number of files with the same format and only data varies in each of them. In the next new build, let us say, the format has been changed or is added with place for a new field. This calls for individual opening and editing of each such file. Note: EDI, WebServices, XML, Configuration files... there are many cases where the test input is a file with a specified format.
62.
63.
64. Template-based File Generator multiple test input files can be created with just one template and one data file Value to Software Testers