Populate the "time" and "timestamp" element in the junit reports

[candrews]

junit xml files can have a "time" attribute on these elements:

• testsuites
• testsuite
• testcase

"time" is the time in seconds that operation took.

This information would be really great to have in the junit reports so one can tell how long each part of the nightwatch test took. For example, in my current project, nightwatch is taking a very long time, but we don't know which tests are the taking the most time.

[candrews]

I've been banging my head on implementing this for a past few hours, and I just can't figure out where to set the start and finish times for each level. The code is really hard for me to wrap my mind around... I'm sure someone more familiar with nightwatch could have this done in minutes. :-/

[beatfactor]

isn't it in milliseconds?

[beatfactor]

it would be a very useful addition and I was just thinking about this the other day. I think the queue.js is the place to start.

[beatfactor]

Just so you know I am implementing command timers. The time is shown per command so not per assertion, since an assertion has often multiple commands. And since the testcases in the junit reports are actually assertions the time will not show up in there for now. You will be able to see the elapsed time for a command when running nightwatch with --verbose. Is this acceptable for you?

[candrews]

@beatfactor that sounds like it would be very useful! Could you sum the times of the commands that compose an assertion to get the assertion time?
For the "testsuites" level time, I was thinking that saving the time when that test started, then when it ended, compare the current time to the saved time and that's testsuits/time. The same clock/different approach could be used the "testsuite" level too.

[beatfactor]

This has been implemented in v0.6.