Which TWO additional structure-based test design techniques could be used to dynamically test the code? 1 credit [K2]

Question

Options

• ACondition testing
• BMultiple condition testing
• CEquivalence partitioning
• DCause/effect graphing
• ECode reviews

• A
  84% (16)
• C
  11% (2)
• E
  5% (1)

Explanation

Condition testing (A) and multiple condition testing (B) are both structure-based (white-box) techniques because they target the internal logic of the code - specifically, boolean conditions and their combinations. They are dynamic because they require executing the code to verify that conditions evaluate correctly, making them valid additions to a white-box dynamic test suite.

C (Equivalence partitioning) and D (Cause/effect graphing) are specification-based (black-box) techniques - they derive tests from requirements or input/output behavior, not from code structure. They don't require knowledge of the internal code.

E (Code reviews) is eliminated on two grounds: it is a static technique (no code is executed) and it is not a test design technique at all - it's a static analysis/verification activity.

Memory tip: Structure-based = white-box = you can see the code's internals. The word "condition" is your clue here - condition testing and multiple condition testing both target the logical conditions (if/else, boolean expressions) inside the code, which requires structural visibility. If the technique name references inputs, outputs, or requirements without mentioning code internals, it's likely black-box.

No community discussion yet for this question.