Page 222 - DCAP405_SOFTWARE_ENGINEERING

Unit 12: Testing Tactics

 Black box testing is a software testing techniques in which functionality of the Software Notes
Under Test (SUT) is tested without looking at the internal code structure, implementation
details and knowledge of internal paths of the software.
 The strategy for fault based testing is to hypothesize a set of plausible faults and then
derive tests to prove each hypothesis.

 The objective of fault based testing within an object oriented system is to design tests that
have a higher possibility of uncovering plausible errors.

12.5 Keywords

BVA: Boundary Value Analysis

SUT: Software Under Test

12.6 Review Questions

1. Why testing is more than just debugging? Explain with examples.
2. Explain why the reason of conducting white-box testing largely depends upon the nature
of defects in software?
3. The test is accurate only if the tester knows what the program is supposed to do. Comment.
4. BVA extends equivalence partitioning by focusing on data at the “edges” of an equivalence
class. Explain briefly.
5. Boundary value test cases are obtained by keeping one variable at its extreme and the
other at its nominal value. Discuss with example.

6. How the equivalence classes can be defined?
7. While White Box Testing (Unit Testing) validates internal structure and working of your
software code, the main focus of black box testing is on the validation of your functional
requirements. Which of the two testing is more beneficial explain?
8. In case you push code fixes in your live software system, a complete system check (black
box regression tests) becomes essential. Discuss.
9. Describe how white box testing has its own merits and help detect many internal errors
which may degrade system performance?
10. In Black Box Testing we just focus on inputs and output of the software system without
bothering about internal knowledge of the software program. Analyze.

Answers: Self Assessment

1. program 2. statements

3. integration 4. Cyclomatic
5. inversely 6. implementation
7. system levels 8. behavioral
9. robustness 10. functionality

11. equivalence 12. inputs

LOVELY PROFESSIONAL UNIVERSITY 215