Black-Box Testing techniques
At the time of creating black-box testing cases, the input data utilized is significant. There are three techniques for managing the amount of input data needed comprise in software development :
Equivalence Partitioning
An equivalence class is a subset of data which is delegate of a larger class. Equivalence partitioning is a method for testing equivalence classes, while going to test each value of the larger class. As per example a program which edits credit limits of any account within a given range bound of 2,000 – 2,500 will have three equivalence classes:
< 2,000 (invalid) Between 2,000 and 2,500 (valid) > 2,500 (invalid)
Boundary Analysis
A method which comprises of developing test cases and data, which focuses on the input and output boundaries of any given software development function are called boundary analysis. In that credit limit boundary analysis will test the following test:
Low boundary +/- one (1999 and 2,001)
on the boundary (2,000 and 2,500)
Upper boundary +/- one (2,499 and 2,501)
Error Speculation
Some test cases may be created upon the perceptions and experience of the tester. As per example in an example where one of the inputs is the date, a tester may try March 29, 2005.
White-Box Testing techniques
White-box testing presumes that the all the path of logic in a unit or program is known. White-box testing software development comprises of testing paths, branch by branch, to create conventional results. Some of the white-box testing methods are:
Statement Coverage
Test engineer must execute all statements at least once.
Decision Coverage
Execute each presumed decision direction at least once.
Condition Coverage
Execute each decision with all possible outcomes at least once.
Decision/Condition Coverage
Execute all likely mixture of condition outcomes in each decision. Treat all iterations as two-way circumstances software development exercising the loop zero times and one time.
