Control Repetitive Power Reboot Testing via Perl Script

Repetitive power reboot regression testing plays a vital role in the product development lab, by providing product designers with a simple effective means to determine how new products will react to repeated power On/Off cycles. Although the basic process of repetitive reboot testing is fairly simple, the continuous, repeated nature of this type of test can often prove to be somewhat of a challenge for those who are responsible for it. For this reason, it can be helpful to automate the test process by using Perl script to initiate each power reboot cycle.

In a typical repetitive power reboot regression test, the device being tested is connected to both a switched PDU and a data collection device. The switched PDU is used to initiate each reboot cycle, while the data collection device is used to capture any error messages or status reports that might be generated as the test device recovers from each reboot cycle. Data collected during the test helps product development engineers to detect hardware problems, firmware bugs and other issues that need to be resolved before the product is released to market.

In order to successfully automate the repetitive power reboot test process, the switched PDU must support control by script; in this example, Perl script is used to control the test process. This eliminates the need for most human oversight of the test procedure, and also helps to improve the reliability and consistency of results by ensuring that each reboot cycle is performed according to schedule, at regular intervals and without interruption. In addition to providing script control, advanced PDU products often include other features that can add capabilities to the test process. Authentication and security related features help to ensure that the repetitive reboot test can be accessed and monitored via network without interference from unauthorized users. Alarm and monitoring features can also be very useful in keeping administrators better informed as to critical conditions and events in the test environment.

Tags: , , , ,

Comments are closed.