Description of problem: In recent packages, I found some SUSPEND tests pass with only "suspend to mem" tested, the exit code is "0". I paste some example here: Example 1: https://hardware.redhat.com/results.cgi?cert_id=507414&id=178622 Only "suspend to mem by OS" tested here, but this test is recognized as "PASSED" Example 2: https://hardware.redhat.com/results.cgi?cert_id=507414&id=178605 Only "suspend to mem by OS" and "suspend to mem by function key" are tested here, but this test is also recognized as "PASSED" Version-Release number of selected component (if applicable): hts 5.3-17 How reproducible: Do "SUSPEND" test with hts 5.3-17 on RHEL5. Actual results: Only one or two features are tested, but this test is still recognized as "PASSED" Expected results: All four tests: "suspend to mem by OS", "suspend to mem by function key","hibernate to mem by OS" and "hibernate to mem by function key" should be tested. *Only* after all of them succeed, the "SUSPEND" can pass.
I believe you're describing expected behavior. The suspend test is required to accompany all other tests where the system provides it. In this case the point is to verify that the network card for example continues to function after a suspend/resume cycle. This variation of the suspend test accompanies all runs on systems with batteries and only does the OS controlled suspend to ram. In addition the full 4 cycle suspend test is required on the same systems to verify that all of the supported suspend modes operate.