Domain Testing

Introduction to Domain Testing

Domain Testing is a software testing technique in which application is tested by providing input data and verification of relevant output. Domain testing also called equivalence testing or boundary analysis testing. In domain testing, testing takes place with the minimum number of input data so that the application does not allow invalid and out of range data and evaluate the expected range of output. Domain testing ensures that an application does not have input data outside the mentioned valid range. This testing process is used to verify the application for its ability to react or operate for different variety of input values.

Top 4 Strategies of Domain Testing

Now let’s discuss the domain testing strategy:

It is divided into sub-domains. After that application considered for domain testing along with sub-domain, in that, single or combination of input data tested through sub-domains. It provides simplification of complex scenarios as domain partitioned into sub-domain. The test conducted at the boundaries of the sub-domain is called Boundary Value Analysis (BVA). When the test conditions are divided into sets or groups of tests, then it named Equivalence Class testing. Domain tester needs to understand about the domain in detail.

1. Domain Selection

The domain which has less complex functionality can be considered domain testing. In the application, there will be input variables that need to be assigned, and the proper result has to be verified.

2. Group the Input Data into Classes

A similar type of input data is partitioned into subsets. There are two types of partitioning, Equivalence class partitioning & Boundary value analysis (BVA). Equivalence class partitioning splits the input into equivalent data partitions to determine test cases. Here, the test cases are designed in such a way that each partition is covered for once. In Boundary value analysis (BVA) testing, test cases are designed considering boundary values invalid range.

3. Input Data of the Classes for Testing

The boundary values should be considered as the data for testing. Boundaries represent the equivalence classes more likely to find an error than the other class members. A data in between the range is the best representative of an equivalence class.

4. Verification of Output Data

When input data is assigned to application concerning that output data verified. Output data should be invalid and specified range.

Examples of Domain Testing

Let’s consider two scenarios as an example:

1. A Test Data with Single Input

Consider x & y are the input variable for any expression and variable z is the output. Here, an expression is a single input scenario that includes variable x & y, hence there is no combination input variable.

Expression examples:  (z =x + y) or (z= x-y) or (z= x*y) or (z=x/y) etc.

2. A Test with Multiple Input Variable

In this example, multiple or combinations of input variables are tested concerning the appropriate output. Let’s consider a School Management application for children grading system, concerning their grading system classes are assigned to them.

According to the above test conditions below scenarios can be determined:

• Scenario1: Student scores > 80 & <=100, with Science subject should be in class A.
• Scenario2: Student scores > 80 & <=100, with Accounts subject should be in class B.
• Scenario3: Student scores < =80 & >65, Science subject should be in class C.
• Scenario4: Student scores < =80 & >65, Accounts subject should be in class D.
• Scenario5: Student scores < =65 & >50, Science subject should be in class E.
• Scenario6: Student scores < =65 & >50, Accounts subject should be in class F.
• Scenario7: Student scores < =50, Science subject should be in class G.
• Scenario8: Student scores < =50, Accounts subject should be in class H.

Here, in the above example, the input will be Marks & Subject, concerning those classes that will be allocated. This case is of the partition of inputs or grouping of input values. The scored marks range are partitioned into the following classes:

• Class 1: Students who scored > 80 & <100.
• Class 2: Students who scored <=80 & >65.
• Class 3: Students who scored <=65 & >50.
• Class 4: Students who scored <=50.

The boundary values should be considered as the data for testing, boundaries represent the equivalence classes that aim to find an error or bug than other class members. A data in between the range is the best representative of an equivalence class. For each class mentioned above, the test required.

For Class 1, students who scored above 80 (marks> 80 & marks <=100).

Boundary values:

• Marks 80 should not be considered in this class, as values should be greater than 80.
• Marks 81 should be considered in this class, as values should be greater than 80.
• Marks 100 should be considered in this class, as values should be lesser than 100 or equal to 100.
• Marks 101 should not be considered in this class, as values should be lesser than 100 or equal to 100.

Equivalence partition Values: The input values from 81 to 100 are valid, hence one of the values between 81, 82, 83 upto100 have to be included. Hence the selected marks “90” are valid marks for this class.

Verification of Output Data

Here from each partition, only one test condition is executed. If one test condition works correctly in a partition, then all the remaining test conditions should work correctly. And, if one test condition in the partition doesn’t run correctly then it is assumed that no other conditions will work correctly.

Structure of Domain Testing

The structure is explained below:

• Analyze the application concerning the domain.
• Find out valid input variables.
• Concerning output find, analyze input variables and sort them.
• Concerning BVA & Equivalence partition analysis create/find input variables.
• Find and analyze output variables concerning input variables.
• Find unanalyzed input variables. Collect information for further evaluation.
• Summarize whole test analysis concerning risk tables.

Conclusion

It is a software testing technique, that requires basic knowledge in the domain to test with the right input to effectuate the necessary output. Domain needs to be divided into sub-domains to perform effectively. It is also termed as equivalence testing or boundary analysis testing, where input variables analyzed and identify as boundary values and equivalence class values to achieve the expected result.

Recommended Articles

This is a guide to Domain Testing. Here we discuss Introduction to Domain Testing and its Testing Strategy, as well as structure with Example. You can also go through our other suggested articles to learn more –

1. Levels of Software Testing
2. Manual Testing
3. What is Test Case?
4. Manual Testing vs Automation Testing