And for the fwts_wakealarm test, a quick fix will be just as Sylvain suggested in comment #2, add it into the QA_TESTS list. And we will be able to remove these two test cases from the test plan (as they will be tested with the fwts_desktop_diagnosis test).
So for now I would like to know do we need these test cases explicitly in the test plan, or can we just integrate them into the fwts_test (to me, I think it's safe to integrate them, as we already done this for the uefirtvariable for a while, and there is no other job depends on the fwts_wakealarm test, unless we're having these for some specific reason)
We do have uefirtvariable test in the fwts_test script of the QA section:
QA_TESTS = ['acpitests',
'acpidump' ,
'acpitable s',
'apicinsta nce',
'bios32' ,
'dmicheck' ,
'mpcheck' ,
'uefirtvar iable',
'version' ]
'aspm',
'ebda',
'msr',
'nx',
And for the fwts_wakealarm test, a quick fix will be just as Sylvain suggested in comment #2, add it into the QA_TESTS list. And we will be able to remove these two test cases from the test plan (as they will be tested with the fwts_desktop_ diagnosis test).
So for now I would like to know do we need these test cases explicitly in the test plan, or can we just integrate them into the fwts_test (to me, I think it's safe to integrate them, as we already done this for the uefirtvariable for a while, and there is no other job depends on the fwts_wakealarm test, unless we're having these for some specific reason)