Power Manager States Test (Compact 7)
3/12/2014
The Power Manager States Test verifies the system power states through the use of the Power Manager APIs.
Test Prerequisites
Your device must meet the following requirements before you run this test.
The following prerequisites are required for this test.
Hardware Prerequisites:
In order to run the test, the platform and/or device drivers should have power management capabilities.
Software Prerequisites:
Having the SYSGEN_PM sysgen variable set when building your OS image will include the Power Manager.
The following table shows the software requirements for this test.
| Requirement | Description |
|---|---|
Tux.exe |
Tux test harness that executes the test. |
Kato.dll |
Logging engine that logs test data. |
pwrtststates.dll |
Test library. |
Subtests
The table below lists the subtests included in this test.
| SubTest ID | Description |
|---|---|
1 |
Power Manager System Power State Tests Usage Message. |
101 |
Test list of supported system power states |
102 |
Test SetSystemPowerstate and GetSystemPowerState APIs - set power to On, UserIdle, ScreenOff. |
103 |
Test Setting SystemPowerstate to Reboot using the power state name. |
104 |
Test Setting SystemPowerstate to Reboot using the power state name and POWER_FORCE flag. |
105 |
Test Setting SystemPowerstate to ColdReboot using the power state name. |
106 |
Test Setting SystemPowerstate to ColdReboot using the power state name and POWER_FORCE flag. |
107 |
Test Setting SystemPowerstate to Off using the power state name. |
108 |
Test Setting SystemPowerstate to Off using the power state name and POWER_FORCE flag. |
109 |
Test Setting SystemPowerstate to Reset using the power state hint. |
110 |
Test Setting SystemPowerstate to Reset using the power state hint and POWER_FORCE flag. |
111 |
Test Setting SystemPowerstate to Off using the power state hint. |
112 |
Test Setting SystemPowerstate to Off using the power state hint and POWER_FORCE flag. |
113 |
Test Setting SystemPowerstate to Critical using the power state hint. |
114 |
Test Setting SystemPowerstate to Critical using the power state hint and POWER_FORCE flag. |
Setting Up the Test
This test has no additional requirements beyond the standard test environment setup.
Running the Test
The Power Manager States Test executes the tux -o -d pwrtststates.dll command line on default execution.
This test library can have one or more optional command line entries to change the behavior of the test. To specify one or more command line entries to the test library, you must use the -c command-line option. This option forces Tux to pass the specified string into the test library.
The following table shows the optional command line parameters for this test.
| Command Line Parameter | Description |
|---|---|
PdaVersion |
Informs the tests that this is a PDA-type device which tests a separate set of system power states. |
Verifying the Test
Many of the tests will reboot the device and a user needs to verify the reboot occurs. When the system reboots, the user should proceed to the next test and begin execution. For this reason, the user may want to execute the tests individually, instead of as a suite.
Troubleshooting the Test
* The platform must have power managment capabilities.
* The platform must support the standard power states used in this test which target the DEFAULT and PDA versions of the Power Manager.
* Ensure the device drivers that will be affected by the reboots are power aware and can handle the system rebooting.
For additional platform specific issues, consult the CTK articles on the TechNet wiki.