[
https://issues.apache.org/jira/browse/SUREFIRE-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14905489#comment-14905489
]
ASF GitHub Bot commented on SUREFIRE-1144:
------------------------------------------
Github user Tibor17 commented on the pull request:
https://github.com/apache/maven-surefire/pull/96#issuecomment-142758232
@lamyaa
Did you have time to run this test using the fix we talked about in
`SUREFIRE-1144`?
Is the execution time calculation broken ?
If it is not broken, we can continue with this. I would rather talk with
Andreas before making any conclusion in this PR. First of all I will test rerun
together with HTML repor. Having `time` in partial executions within testcase
is maybe releval statistics. The only problem is with `failure` because it does
not have `time` in testcase without rerun. There is also another problem with
`time` in `failure` when JUnit tests use `ErrorCollector` which reports
multiple failures in testcase which needs to be tested in current release
2.18.1. The problem is that the time of such failures is not aggregated in
reality and thus individual times match the sum and the individual times are
not necessary. I guess the only failures and rerunFailure elements may have
`time` if and only if rerun is applied in such testcase.
Currently this decision is not trivial for me to make because I need to
make more investigations of current status.
> Time for testsuite on commandline does not suit with the time value given in
> the report file
> --------------------------------------------------------------------------------------------
>
> Key: SUREFIRE-1144
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1144
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 2.18
> Reporter: Karl Heinz Marbaise
> Assignee: Tibor Digana
> Priority: Critical
> Fix For: 2.19
>
> Attachments: mvn.log, surefire.reports.tar.gz
>
>
> Currently i have a build where i got printed out the following:
> {noformat}
> [INFO] --- maven-surefire-plugin:2.18:test (default-test) @ supose-cli ---
> [INFO] Surefire report directory:
> /Users/kama/ws-git/supose/supose-cli/target/surefire-reports
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running com.soebes.supose.cli.SuposeCLITest
> Configuring TestNG with: TestNG652Configurator
> Tests run: 22, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.562 sec -
> in com.soebes.supose.cli.SuposeCLITest
> Results :
> Tests run: 22, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
> {noformat}
> So if i take a look into the appropriate surefire-report file
> {{supose-cli/target/surefire-reports/TEST-com.soebes.supose.cli.SuposeCLITest.xml}}
> i see the following in the first lines:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <testsuite name="com.soebes.supose.cli.SuposeCLITest" time="0.142" tests="22"
> errors="0" skipped="0" failures="0">
> <properties>
> {code}
> which shows a complete different time {{0.142}} instead of {{0.562}}.
> I have had expected to see the same time in the xml file as well as on the
> print out on console...
> So the question is: Where does this difference come frome? Do i misundestand
> a thing here?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
