causten
commented
8 years ago I think the right solution is to move this test suite to a separate directory instead of 'tests'. The reason why is because it has nothing to do with the code stack. It has to do with trying to break a specific thing. It was designed to test yanking the AC to a system time and time again. So it isn't a good test to verify a commit. It would be a great Driver Verification Test or weekly long run buster type program.
I vote to create a new directory designed to hold buster programs.
gkeishin
We have to stream line how the test case execution is done.. No preset environment variables, the entire test suite for a barreleye system $ OPENBMC_HOST=x.x.x.x tox -e barreleye -- tests
If we are running the suite like this.. the bellow breaks since those PDU info are not populate..
Set the power restore policy
Full Name: Tests.Test Power Restore.Set the power restore policy Documentation:
This test case sets the pilicy as given under the policy attribute. ExpectedSystemState:-is the state where system should be before running the test case NextSystemState:-is After Power cycle system should reach to this state if the system is not at the Expected System State,This test case brings the system in the Expected state then do the power cycle. Start / End / Elapsed: 20160530 23:25:10.072 / 20160530 23:30:14.025 / 00:05:03.953 Status: FAIL (critical) Message: Several failures occurred:
1) Unable to find variable PDU_TYPE
2) Unable to find variable PDU_TYPE
3) Unable to find variable PDU_TYPE
4) Unable to find variable PDU_TYPE
5) Unable to find variable PDU_TYPE
6) Unable to find variable PDU_TYPE
7) Unable to find variable PDU_TYPE
By default, these data are not populated...
lib/resource.txt
PDU related parameters
${PDU_TYPE} ${EMPTY} ${PDU_IP} ${EMPTY} ${PDU_USERNAME} ${EMPTY} ${PDU_PASSWORD} ${EMPTY} ${PDU_SLOT_NO} ${EMPTY}
Either we have add exclude in the tox.in to skip those test or have it automated in the code resource file..