Structure Based Technique White Box

Structure based testing is a strategy in which testing is based solely on the internal working and structure of the code. Testing is based on the internal paths, structure, and implementation of the software under test (SUT). In contrast to its complement, black box testing, it generally requires detailed programming skills.
Structure based testing is commonly referred to as "white box testing". It is also called as "Glass box" or "Clear Box" testing.

Process involved in white box testing are follows:

1. Analyze the SUT's implementation and then identify paths through the SUT.
2. Choose the inputs to cause the SUT to execute selected paths. Expected results for those inputs are determined.
3. Execute the tests. Actual outputs are compared with the expected outputs.
4. A determination is made as to the proper functioning of the SUT.

Notre: The tester must have programming skill to understand and evaluate the SUT.

White box testing comprises following techniques under static and structural testing:
Desk checking
Code walkthrough
Formal or fagan inspection
statement coverage
Flow graph and path testing
Data flow testing
syntax testing

How To use All Pairs Technique Testing

All PairsTesting: It is also known as Pairwise Testing Technique which is a combinatorial software testing method where, for each pair of input parameters to a system, all possible discrete combinations of those parameters are identified and tested.

In this method, a set of test cases is generated that covers all combinations of the selected test data values for each pair of variables. It's also referred as 2-way testing. It is also possible to do all triples or all quadruples testing, but the size of the higher order test sets grows very rapidly.

This technique normally begins by selecting values for the system's input variables. These individual values are often selected using domain partitioning. The values are then permuted to achive coverage of all the pairings.

The steps for using all pairs testing technique follows:
STEP 1: Analyze the given test inputs or requirements and list out the variables in the application to be tested. This can be listed in the form of a table where column headers represent the various variables to be tested.

Note: Equivalence class partitioning technique can also be used at this point to partition and group together variables.

STEP 2: List out the various possible values each of the variables can hold. These values can be put in rows just beneath the corresponding variables.

STEP 3: Create the "ALL Pairs" table by putting the variables in the top row and start by filling in the values for the variables in each column.

STEP 4: If a combination does not exist, then swap around with the values to see if the combination can be got.

STEP5: Else add a new row