Description of problem: The enable/disable test option does not work properly after the first run. The user cannot change a test’s enable/disable status after the kit has run once, no matter if that test was run or not. Version-Release number of selected component (if applicable): HTS 5 release 14 How reproducible: This is an example using the virt test hts discovery hts plan hts print disable Test: hts plan --disable --test=virt Try and run test, when you shouldn’t be able to (it only runs INFO, which is correct) hts certify --test=virt Enable Test: hts plan --enable --test=virt run the test again to show that is truly disabled: hts certify --test=virt Actual results: Never enables test, nor runs the test. Expected results: It should enable the test. Additional info: The testkit seems to be grabbing the enable/disable parameter from the /var/hts/results.xml file, instead of from the /var/hts/config.xml file. The config.xml displays what it is supposed to run, while the results.xml file displays what was previously run. The “disabled=’true’” entry in the results.xml must be deleted for the test to be enabled.
Fixed R16.
Please verify this fix.
Fixed.