When we start developing software the initial step is to develop is “units” i.e. the smallest building block of software. Later on all these units collaborate together to work as complete software or an application. So correct working of these small units is very essential because their working describe the complete functionality of the software or application.
Why go through Unit testing:
- Easy to find bugs in small units.
- Able to debug the internal functionality of software that is not easy to debug at the time of testing of complete software.
- Able to go through the structural code coverage of software/application.
- Able to debug the software without waiting for the other modules or parts of software to be developed.
Why using tools of unit testing:
Unit testing is little bit boring kind of thing. A tester has to create test cases that may or may not release any fault. In unit testing test cases are defined to check the code or functionality of the units. That’s why test cases are developed according to the code and it will be change as the code of units is change. Tester has to perform repetitively testing of a small unit of software with different number of input values. Unit testing will some time face serious problem after any small or simple modification in code of software. Means it will become hard some time to perform unit testing of modification or updating software.
Unit Testing Techniques:
Numbers of techniques are available for software testing now but usually they are not useful. Some of techniques are:
1. Functional Testing Techniques.
- Boundary Value Analysis.
- Equivalence Partitioning.
- Cause Effect Graphing.
2. Structural Test Case Techniques.
- Statement Coverage.
- Branch Coverage.
- Condition Coverage.
- Modified Condition-Decision Coverage.
3. Heuristic Testing.-Numbers of frameworks are available for different programming languages like c, c++, c#, java, ABAP etc.
0 comments:
Post a Comment