If a test time is less than 1 second it is rounded to the nearest millisecond. Anything less than 1 millisecond is still omitted.
Changes
test estimates will now be in s or ms based on the time provided in the junit xml.
Potential impacts
Any existing tests reporting time under 1 second will start to see times posted in testrail. While I see this as a bug, others may have usecases where this is unexpected as they have worked with the current behavior.
Steps to test
Upload any junit with a time < ".5" and confirm the test is uploaded with the estimate in ms
Issue being resolved: https://github.com/gurock/trcli/issues/95
Solution description
If a test time is less than 1 second it is rounded to the nearest millisecond. Anything less than 1 millisecond is still omitted.
Changes
test estimates will now be in
s
orms
based on the time provided in the junit xml.Potential impacts
Any existing tests reporting time under 1 second will start to see times posted in testrail. While I see this as a bug, others may have usecases where this is unexpected as they have worked with the current behavior.
Steps to test
Upload any junit with a time < ".5" and confirm the test is uploaded with the estimate in
ms
PR Tasks