[jira] (SUREFIRE-970) Elapsed time of skipped tests in surefire report XML file shows huge number

[Kristian Rosenvold (JIRA)]

    [ 
https://jira.codehaus.org/browse/SUREFIRE-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=321777#comment-321777
 ] 

Kristian Rosenvold commented on SUREFIRE-970:
---------------------------------------------

This is our favourite feature to break in surefire ;) The main cause of this is 
that determining the actual execution time of the test has been (legacy) 
determined in the provider. I have been moving this towards being fully 
established in the reporting system, since that would solve it once and for 
all, and make just a handful of testcases sufficient to test all the providers 
on this. So removing duplication of responsibilities is what this is about ;)
                
> Elapsed time of skipped tests in surefire report XML file shows huge number
> ---------------------------------------------------------------------------
>
>                 Key: SUREFIRE-970
>                 URL: https://jira.codehaus.org/browse/SUREFIRE-970
>             Project: Maven Surefire
>          Issue Type: Bug
>    Affects Versions: 2.13, 2.14
>            Reporter: Andreas Gudian
>
> E.g., for a test class with {{@Ignore}}:
> {code:title=com.foo.ApplicationConfigurationTest.txt}
> -------------------------------------------------------------------------------
> Test set: com.foo.ApplicationConfigurationTest
> -------------------------------------------------------------------------------
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.03 sec
> {code}
> {code:title=TEST-com.foo.ApplicationConfigurationTest.xml}
>   <testcase name="com.foo.ApplicationConfigurationTest" 
> classname="com.foo.ApplicationConfigurationTest" time="1,512,218.245">
>     <skipped message="expected:&lt;[custom]&gt; but 
> was:&lt;[${custom.property}]&gt;"/>
>   </testcase>
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira