-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
Move away from collecting CI jobs test results in a custom file in favor of JunitXML
-
22
-
False
-
-
False
-
Not Selected
-
Proposed
-
Proposed
-
To Do
-
Proposed
-
Proposed
-
10% To Do, 10% In Progress, 80% Done
-
-
Historically we have used custom file in order to collect test results of our feature verification tests e.g. Autoscaling custom tests,Logging tests and everything that is not Tempest tests. Right now Jump tool knows to accept and parse two kind of test result files:
1.JunitXML
2.Custom file that should be written in a certain format
Right now we are using Jump that can work with both JunitXML and custom files. There is a requirement from CI/Polarion team to start using exclusively JunitXML format to store test results because there is a plan to get rid of Jump and use a different tool for updating Polarion and this tool will accept only JunitXML format.
We have to scope this work for after OSP18GA. Investigate how to make a transition to JunitXML and prioritise .
- account is impacted by
-
OSPRH-8378 Investigate XML reporting that done by netwroking DFG and see if that could work for us.
- Closed