Software Testing Methodologies:
- White Box Testing
- Black Box Testing
- Grey Box Testing
White Box Testing:
White Box Testing is also known as clear box testing, glass box testing, code box testing. It is usually performed by developers. In this type of testing, code is visible to the tester. White Box testing is based on the inner working of an application. Internal Testing is done in this phase. In white-box testing the inner working of software is visible.
White Box Testing Techniques:
- Statement Coverage
- Branch Coverage
- Path Coverage
- Condition Coverage
- Multiple Condition Coverage
- Decision Coverage
- Control Flow Testing
- Data Flow Testing
This Technique Requires every possible statement in the code to be tested at least once. It is used to calculate the total number of executed statements in the source code out of the total statements present in the source code.
Statement Coverage = (Number of executed statements/Total Number of statements) * 100
For eg: Number of executed statements = 5
Total Number of statements=7
Now Statement Coverage= 5/7*100=71%.
Series of tests to ensure that all the branches are tested at least once. Branch Coverage works on the basis of If-Else condition.
All possible path which means each statement and branch is covered. In this technique, we use source code of the program so that we can find every executable path.
White Box Testing Tools:
- Parasoft Jtest
- Google test
- In White Box Testing, code is optimized by finding hidden errors.
- White Box test cases can be easily automated.
- Provides clear rules when testing needs to be stopped.
- It can be expensive.
- White box testing can be complex.
- White box testing is time-consuming.
- It can be possible that we sometimes miss some lines of code that need to be tested.
- In-depth knowledge about a programming language is required when you are performing white box testing.