1. Purpose and scope
The first working program is rarely the cheapest. Tests are added during debug, guard bands are wide and every test runs on every part. This stage brings the cost of test down to the target in the cost model before volume starts, while keeping the quality the strategy asked for.
Each kind of reduction carries a different quality risk. Running more parts in parallel or reordering patterns changes little; removing or sampling tests, or adapting tests from data, changes what is screened and must be justified and reviewed. The stage ends when the test time target is met with every reduction approved.
12 more sections for registered members.