Repetitive Power Reboot Regression Testing Controlled by TcL Script

Although repetitive power reboot regression testing provides a powerful tool for product developers seeking to track down problems before a new product is released, it is also an incredibly tedious process that can stretch on for weeks, or even months. One simple way to eliminate the tedium from repetitive power reboot regression testing is to use TcL script to control power On/Off switching activities.

When repetitive power reboot regression testing is controlled by TcL script, a new reboot cycle can be automatically triggered after the previous reboot cycle is complete, without the need for constant human oversight. The script used to drive power On/Off switching is generally fairly simple, basically boiling down to a long series of power switching commands. As each switching action is completed, the next script in line is issued to begin a new reboot cycle.

In a typical power reboot regression test application, the device being tested is connected to both a switched PDU and a data collection device. The switched PDU is employed to execute each reboot cycle and the data collection device is present to capture any error messages or status reports that are generated when the test device recovers from each reboot cycle. When control by TcL script factored into the application, script commands are issued to the switched PDU, either locally via console port or remotely via SSH. Each switching command causes the switched PDU to begin a new reboot cycle.

The most critical element in this type of script-driven testing, is the presence of a switched PDU that can be controlled via TcL Script. WTI’s VMR series Outlet Metered PDUs provide the perfect fit for power reboot test applications that are controlled via TcL script. In addition to providing full support for TcL scripting, the VMR also includes a formidable assortment of security and authentication features to ensure that remote communication with the PDU is secure, plus versatile, innovative monitoring and alarm features that help test administrators to keep track of exactly what’s going on in the test environment.

Tags: , , , , ,

Comments are closed.