You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to TeamCity's documentation, the testFinished service message can take a duration attribute that specifies the amount of time a test has taken:
The current teamcity.psm1 only accepts the name attribute. While that certainly satisfies most cases and will cause TeamCity to measure the time by the span between the testStarted and testFinished messages, I recently had a need for this where I spawned concurrent jobs to hit http endpoints and then come back with results. Each job tracked the time taken within its own thread.
I modified the function to optionally take a duration parameter. Pull request coming...
The text was updated successfully, but these errors were encountered:
mwrock
added a commit
to mwrock/psake-contrib
that referenced
this issue
Apr 6, 2012
According to TeamCity's documentation, the testFinished service message can take a duration attribute that specifies the amount of time a test has taken:
The current teamcity.psm1 only accepts the name attribute. While that certainly satisfies most cases and will cause TeamCity to measure the time by the span between the testStarted and testFinished messages, I recently had a need for this where I spawned concurrent jobs to hit http endpoints and then come back with results. Each job tracked the time taken within its own thread.
I modified the function to optionally take a duration parameter. Pull request coming...
The text was updated successfully, but these errors were encountered: