Bulldozer00's Blog

For some context, assume that your software-intensive system can actually be modeled in terms of “identifiable C”s:

Given this decomposition of structure, the ideal but pragmatically unattainable test plan that “may” lead to success is given by:

On the opposite end of the spectrum, the test plan that virtually guarantees downstream failure is given by:

In practice, no program/project/product/software leader in their right mind skips testing at all the “C” levels of granularity. Instead, many are forced (by the ubiquitous “system” they’re ensconced in) to “fake it” because by the time the project progresses to the “Start Formal Testing” point, the schedule and budget have been blown to bits and punting the quagmire out the door becomes the top priority.