Ironically, the biggest problem with repetitive reboot testing is that it is extremely repetitive. Although repetitive reboot testing can yield valuable data during product development, it’s generally a long, drawn-out procedure that can lasts for days or weeks. Obviously, it’s somewhat impractical to assign several employees to constantly oversee the repetitive reboot testing through completion, so many test labs rely on an automated solution to make regular reboot cycles are initiated without interruption for the duration of the test. One popular solution employed in many test labs is to automate repetitive power reboot regression testing using TcL (also known as “Tickle”) script.
Archive for the ‘reboot via TcL script’ Category
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.
Regression testing provides product development engineers with a reliable means for ensuring that hardware and software products can recover gracefully from a power interruption. In order to simplify the process of continually switching the test device on and off, user scripts (typically Bash scripts or TcL scripts) are employed to automate repetitive reboot testing.
Although repetitive power cycle testing provide an effective means to detect hardware flaws and software bugs, setting up this type of test can sometimes be somewhat complicated. One way to simplify repetitive on/off power cycle testing, is to use a switched PDU that is driven by TcL scripts (also known as “Tickle” scripts.)