It is observed that boundary points for any inputs are not tested properly. This leads to many errors. Large number of errors tend to occur at boundaries of the input domain.
Boundary Value Analysis(BVA) leads to selection of test cases that exercise boundary values.
BVA complements equivalence partitioning i.e. select any element in an equivalence class, select those at the ''edge' of the class.
For a range of values bounded by a and b, test (a-1), a, (a+1), (b-1), b, (b+1).
If input conditions specify a number of values n, test with (n-1), n and (n+1) input values.
Apply 1 and 2 to output conditions (e.g., generate table of minimum and maximum size).
If internal program data structures have boundaries (e.g., buffer size, table limits), use input data to exercise structures on boundaries.
BVA and Equivalence partitioning both helps in testing the programs and covers most of the conditions. This method does not test the combinations of input conditions.
Translation of natural language descriptions of procedures to software based algorithms is error prone.
Cause-effect graphing attempts to provide a concise representation of logical combinations and corresponding actions.
Causes (input conditions) and effects (actions) are listed for a module and an identifier is assigned to each.
A cause-effect graph developed.
Graph converted to a decision table.
Decision table rules are converted to test cases.
INTEGRATION TESTING PART ONE
INTEGRATION TESTING PART TWO
INTEGRATION TESTING PART THREE
INTEGRATION TESTING PART FOUR
INTEGRATION TESTING PART FIVE
INTEGRATION TEST STANDARDS
INTEGRATION TEST STANDARDS PART TWO
QUALITY ASSURANCE PART TWO
QUALITY ASSURANCE SQA
QUALITY OF DESIGN OF TEST CASE
QUALITY MANAGEMENT IN SOFTWARE TESTING
TOOLS FOR QUALITY MANAGEMENT
STATICAL QUALITY ASSURANCE
ISO APPROACH TO QUALITY TESTING