Guide for Automated Test Best Practices | Part 2 Deploying Test Systems

Part 2 | The Enjoyment of Deployment - Automated Test Best Practices

As mentioned in Part 1 of this blog series, printed circuit boards (PCBs) are getting more complex every year. The testing goals of most industries seem to be faster, more intelligence, smaller footprint, and of course, less cost. That last one is one of the more vexing problems of the test engineering department. If the product costs less, there is less money for testing, and by inference, less test time as production volumes soar. This is the “fun” part. Let’s explore what this means. 

Now if you happen to work in an industry where the product you are testing has safety liability and in many cases wartime issues, automated testing is far more important than perhaps what the accountants and production managers thought was adequate. Let me elaborate. 

Say you are a test engineering manager in the automotive industry. If you are testing active safety features like anti-lock brakes (ABS) or a collision avoidance system (CAS), and because of inadequate testing, a vehicle crashes and takes lives and property, then the lawyers get involved as lawsuits against the manufacturer cost time and millions of dollars. Can you see why your test strategy must be comprehensive enough and fast enough to provide the most accurate test at the lowest cost?

Now let’s up the ante a bit.  You work in the defense industry… for a manufacturer who won the contract at the lowest cost.  If your test strategy is not accurate enough, that missile or smart bomb may not achieve its mission. So, who wins the war? 

Now I am not faulting accounting or production here.  They all have jobs to do.  My point is that in a safety or defense application, the value of communication to define and justify the most reliable test required – the second C word of this series – is key. 

Your team must understand:

• How much test is needed
• How testing cost affects the sale price
• Which resources are embedded in the PCB
• How much time you have to test each component
• The time to market for your product
• The timeline to get your test systems ready
• The expected volume of products to be tested over the product life cycle is

Let’s look at each of these testing best practices. 

• How much test is enough? A company I used to work for used the acronym JET – Just Enough Test. Engineering should be able to point out the most critical features that must be verified at the final test. Again, communication is crucial at the test system design phase. How to test the functions and what instrumentation is needed? 

• • Again, the decisions here are a balancing act – What is the cost of testing? How much does it affect the sale price per product? What are the liability issues of failure (e.g., Active Safety, military weapons) and in some cases, the company's reputation in the market? 

• What self-test resources are embedded in the PCB? As PCBs get more complex, more intelligence is often added to verify functionality through self-test.  If this is so, how do you enable self-test? How much functionality is covered? Is it faster to verify these functions through self-test or using the test system’s facilities? 
• How much time do I have to get ready? From the moment you get the initial test specification, when will the first PCB appear at my test station? Knowing that info up front lends a certain urgency to your plans.