How many paths are needed for branch testing?

A bound on the number of test cases needed to achieve branch coverage is important to evaluate the effort needed to test a given program. However, the bounds proposed so far in the literature are not effective to measure testing effort. In this article, we introduce a new, meaningful lower bound on the number of test cases needed to achieve branch coverage. We first identify the set of unconstrained arcs in a ddgraph. This is the minimum set of arcs such that a set of paths that exercises these arcs covers all the arcs in the program ddgraph. In general, a path may cover more than one unconstrained are: the strategy we use to combine more unconstrained arcs into one path determines the cardinality of the set of test paths, i.e., the bound we are looking for. It is now commonly accepted that the real problem in branch testing is to derive an executable set of test paths. Therefore, we will consider those control flow paths containing a low number of decisions to be meaningful because they are more likely to be feasible. We formalize this notion by introducing the weak incomparability relation between ddgraph arcs. We then define the new, meaningful bound as the maximum number of unconstrained arcs in a ddgraph that are mutually weakly incomparable. Furthermore, we show that the bound fits into the testability model of Bache and Mullerburg (1990). (C) 1996 by Elsevier Science Inc.