[ https://issues.apache.org/jira/browse/SUREFIRE-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15961785#comment-15961785 ]
Tibor Digana commented on SUREFIRE-1325: ---------------------------------------- [~Bingoko] Having the elapsed time would help me too, but the memory consumption should fixed after I introduce a new format of stream. The format transfers data from forked jvm to Maven process. If you want to you can patch the elapsed time and open pull request in GitHub. > Monitoring the testing memory consumption and printed with elapsed time > ----------------------------------------------------------------------- > > Key: SUREFIRE-1325 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1325 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Surefire Plugin, process forking > Reporter: Bob Li > Labels: profiler > Original Estimate: 12h > Remaining Estimate: 12h > > As the user, the elapsed time for executing the test case is important, but I > think the memory consumption is also important. > I think the maven surefire could printed both of them for the user. -- This message was sent by Atlassian JIRA (v6.3.15#6346)