whitebox-controlflow-basic

Branch (C1) coverage requires exercising both the true and false outcomes of every decision (if, while, switch, ternary) at least once. Enumerate all decisions, assign true/false slots to each, pick inputs that hit each slot, and verify with a branch coverage report.

Decision coverage (C1) only checks that each whole decision evaluates both true and false, while condition coverage checks that each atomic condition inside a compound expression takes both values. Condition coverage alone can miss one decision outcome, so decision/condition coverage combines both.

No. C0 100% only means every executable line ran once; the false side of branches can remain completely untested. Treat statement coverage as a minimum floor in CI, not a quality target, and add branch and condition criteria.

With operators like && and ||, later conditions may never be evaluated for some inputs, so their true/false slots stay unfilled even when coverage looks complete. Choose inputs that force evaluation of every atomic condition.

Use MC/DC when you must show each condition independently affects the decision outcome, such as in safety-critical code. Decision/condition coverage is a cheaper intermediate level that does not prove independent influence.