Test Program development time is under pressure. Often, the tester capability, coding or debug development time due to tester complexity is blamed for the development delay. In some cases, these issues are the cause for the delay, however, often, it is related to the methodology used. This paper will demonstrate, via real examples, how to improve test development time. By developing an optimized test program structure, improving communication between design and test engineers with a common language, and ensuring that all parties are properly trained to efficiently use the tester and the new test program structure, improvements can be realized. This paper discusses the methodology used to decrease test program debug time from first samples to completion from 24 weeks to 12 weeks. During this presentation, we will also take the opportunity to introduce some tools (like DevOps, Portbridge, Oasis...) allowing to help/assist Test Engineers and Designers during Design For Test (DFT), Coding and debug phase .
