Hi Karl,

I think it should. Let me experiment with it and check what's happening. I think you used YAMLish to report the times?

Hmmm, reproduced the issue. So far I have found out that

a) we need better documentation about the duration for test results
b) the diagnostics is not being persisted in the build action, and thus it is always displaying zeroes

Actually, I was looking at an older job I think. Investigating why the total is not the sum of the time of all the tests.

Code changed in jenkins
User: Bruno P. Kinoshita
Path:
src/main/java/org/tap4j/plugin/TapResult.java
src/main/java/org/tap4j/plugin/model/TapStreamResult.java
http://jenkins-ci.org/commit/tap-plugin/826be90000d4876cce1703449050e4a25b4c5423
Log:
JENKINS-24843 Add marker to where to add duration tally code

Code changed in jenkins
User: Bruno P. Kinoshita
Path:
src/main/java/org/tap4j/plugin/TapResult.java
src/main/java/org/tap4j/plugin/model/TapTestResultResult.java
http://jenkins-ci.org/commit/tap-plugin/96365ab5f1d3eabc2c34e436dfa5ce826d6cfcbb
Log:
[FIXED JENKINS-24843] Copy duration from Tabulated Tests

In order to fix it, I had to copy code that is being used in another part of the plug-in. I need to rethink the plug-in design to

1) better support extend tap results and the default jenkins test results (added later)
2) allow builds to scale to million of tests without performance issues

Will include this fix in the next release, but watch out for a future 2.0 release, which may not be fully compatible with older jobs (though I promise I will try to use XStream auxiliary code to keep backward compatibility).

2.0 Released