Software Testing
Code Coverage Tutorial: Branch, Statement, Decision, FSM
What is Code coverage? Code coverage is a measure which describes the degree of which the source...
Practically, due to time and budget considerations, it is not possible to perform exhausting testing for each set of test data, especially when there is a large pool of input combinations.
In this tutorial, we will learn
Boundary testing is the process of testing between extreme ends or boundaries between partitions of the input values.
Equivalence Partitioning or Equivalence Class Partitioning is type of black box testing technique which can be applied to all levels of software testing like unit, integration, system, etc. In this technique, input data units are divided into equivalent partitions that can be used to derive test cases which reduces time required for testing because of small number of test cases.
Here is the test condition
We cannot test all the possible values because if done, the number of test cases will be more than 100. To address this problem, we use equivalence partitioning hypothesis where we divide the possible values of tickets into groups or sets as shown below where the system behavior can be considered the same.
The divided sets are called Equivalence Partitions or Equivalence Classes. Then we pick only one value from each partition for testing. The hypothesis behind this technique is that if one condition/value in a partition passes all others will also pass. Likewise, if one condition in a partition fails, all other conditions in that partition will fail.
Boundary Value Analysis- in Boundary Value Analysis, you test boundaries between equivalence partitions
In our earlier equivalence partitioning example, instead of checking one value for each partition, you will check the values at the partitions like 0, 1, 10, 11 and so on. As you may observe, you test values at both valid and invalid boundaries. Boundary Value Analysis is also called range checking.
Equivalence partitioning and boundary value analysis(BVA) are closely related and can be used together at all levels of testing.
| Test Scenario # | Test Scenario Description | Expected Outcome |
|---|---|---|
| 1 | Enter 0 to 5 characters in password field | System should not accept |
| 2 | Enter 6 to 10 characters in password field | System should accept |
| 3 | Enter 11 to 14 character in password field | System should not accept |
Here we will see the Boundary Value Test Cases
| Test Scenario Description | Expected Outcome |
| Boundary Value = 0 | System should NOT accept |
| Boundary Value = 1 | System should accept |
| Boundary Value = 2 | System should accept |
| Boundary Value = 9 | System should accept |
| Boundary Value = 10 | System should accept |
| Boundary Value = 11 | System should NOT accept |
Summary:
What is Code coverage? Code coverage is a measure which describes the degree of which the source...
In this tutorial, you will learn What are Embedded systems? What is Embedded Testing? Embedded...
What is Functional Testing? FUNCTIONAL TESTING is a type of software testing that validates the...
What is Security Testing? SECURITY TESTING is a type of Software Testing that uncovers...
Banking Domain Testing Banking Domain Testing is a software testing process of a banking...
Smoke and Sanity testing difference is the most misunderstood topic in Software Testing. There is...