TPS Translation Versus Rehost

Test Program Sets (TPS) must sometimes be moved from one platform to another. This can be due to obsolescence of the Automatic Test Equipment, consolidation to a new platform or any number of other reasons. This can involve major modifications to the TPS due to the Test Executive, Programming Language, or many other factors. These factors can increase the cost of TPS development significantly. When moving TPSs one must consider the options involved in moving the TPS. The TPS can be converted by hand or automated processes can be created to help with the task at hand. Choosing automation can involve many factors such as the cost of rewriting the TPS by hand versus creating tools to perform the task. Other factors such as future proofing the TPS against future conversions must also be considered since Unit Under Test (UUT) can have a long lifetime. One way to help with future migrations is to use modern tools to create requirements for the Test Program that can later be used to generate the Test Program automatically or semi-automatically. This paper will cover some of the things to consider as well as some lessons learned in order to move a Test program to a new platform in a cost effective manner.