Measure test run time duration #426
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Was thinking about |
milo
added a commit
that referenced
this pull request
Jan 2, 2021
dg
pushed a commit
that referenced
this pull request
Jan 31, 2021
dg
pushed a commit
that referenced
this pull request
Feb 5, 2021
dg
pushed a commit
that referenced
this pull request
Mar 1, 2021
dg
pushed a commit
that referenced
this pull request
Mar 1, 2021
dg
pushed a commit
that referenced
this pull request
Mar 1, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It is a quite hard to measure test run time duration precisly. It is possible from test itself, but things get complicated with
@testCaseand@providerannotations when collecting/pairing durations back to custom output handler.I think that this kind of measurement is quite precise and easy to access for OutputHandler.
Time duration is unnecessary most of the time, but it is very useful when reducing total amount of time with higher quantity of tests (100+). For examle, database locks or php.ini tunning (e.g. loading SNMP extension eats hundreds of miliseconds).