Description of problem: During an interactive test run, a button labeled "stop" appears on the page. This button does not actually stop the current test. Version-Release number of selected component (if applicable): 20150520 How reproducible: reliably Steps to Reproduce: 1. start a certification 2. launch an interactive test 3. during testing, click the "stop" button on the interactive test's page Actual results: certification page is loaded. current status of test indicates that it is waiting for user input. returning to the host's test page shows the same test interaction. new tests cannot be loaded, and test cannot be skipped. Expected results: "stop" button ceases current test run and reloads the host (or certification) page. Additional info: tested this with cd-rom test in -hardware
This bug blocks the ability to abort the current test run.
closing the certification, from the certification screen listing all hosts, does not resolve the problem, and does not appear to close the certification.
Relabelng the button to be "restart", since that's what it really does. The expected behavior is that the test run will restart, so an interactive test will return to the first prompt in the test.
currently the "restart" button is skipping the test being run. When I ran a test on a laptop system that always requires the suspend / hibernate tests, clicking "restart" skipped ahead to the intended test. Does this need to be fixed?
(In reply to Brian Brock from comment #6) > currently the "restart" button is skipping the test being run. > > When I ran a test on a laptop system that always requires the suspend / > hibernate tests, clicking "restart" skipped ahead to the intended test. > > Does this need to be fixed? What is the "intended test"?
the test that was selected to be run, instead of the mandatory tests added to the list.
Cloned suspend test issue to bug 1277191
verified in redhat-certification-2.0-20151030.el7 The original bug described has been fixed, the new issue seen is reflected in the new clone.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-2479.html