Handling continuously failing test cases while running entire test bucket.
This change includes:
- Added known_issue tag for test cases failing due to existing issues.
And where fix for the issue is expected to take little long time.
- With each tag addition also added github issue number.
Benefits:
- Failing test cases can be excluded while running entire bucket
using --exclude known_issue as suffix
- Continuously failing test cases will have related issue number
in document section.
Change-Id: I18c40b97a25eff947a5922e4abfacde07fe19a6b
Signed-off-by: Rahul Maheshwari <rahulmaheshwari@in.ibm.com>
diff --git a/tests/test_occ_powercap.robot b/tests/test_occ_powercap.robot
index 02f1a26..31471f9 100644
--- a/tests/test_occ_powercap.robot
+++ b/tests/test_occ_powercap.robot
@@ -22,6 +22,9 @@
[Documentation] This testcase is to test get/set powercap feature.
... In the testcase we are reading min, max value and then
... try set the random in that range.
+ ... Existing Issue: https://github.com/openbmc/openbmc/issues/552
+ [Tags] known_issue
+
${min}= Get Minimum PowerCap
log ${min}
${max}= Get Maximum PowerCap
@@ -38,6 +41,9 @@
Set Less Than Minimum PowerCAP
[Documentation] Test set powercap with less than min powercap value
+ ... Existing Issue: https://github.com/openbmc/openbmc/issues/552
+ [Tags] known_issue
+
${org_power_cap}= Get PowerCap
${min}= Get Minimum PowerCap
${sample_invalid_pcap}= Evaluate ${min}-${100}
@@ -49,6 +55,9 @@
Set More Than Maximum PowerCAP
[Documentation] Test set powercap with more than max powercap value
+ ... Existing Issue: https://github.com/openbmc/openbmc/issues/552
+ [Tags] known_issue
+
${org_power_cap}= Get PowerCap
${min}= Get Maximum PowerCap
${sample_invalid_pcap}= Evaluate ${min}+${100}