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
The excellent gotestsum tool has a feature to show the slowest tests:
Usage:
gotestsum tool slowest [flags]
Read a json file and print or update tests which are slower than threshold.
The json file may be created with 'gotestsum --jsonfile' or 'go test -json'.
If a TestCase appears more than once in the json file, it will only appear once
in the output, and the median value of all the elapsed times will be used.
[...]
Flags:
--debug enable debug logging.
--jsonfile string path to test2json output, defaults to stdin
--skip-stmt string add this go statement to slow tests, instead of printing the list of slow tests
--threshold duration test cases with elapsed time greater than threshold are slow tests (default 100ms)
It would be nice if this list was available on a separate tab/page, with links ?
Example output of tool, after make out/unittest.json and "DONE 899 tests, 2 skipped in 13.313s"
BTW: something is fishy here, go-test-report says 895 (not 899) "✓ Passed: 893 ‐ Skipped: 2 ✗ Failed: 0" ? --> filed Bug #19
The excellent
gotestsum
tool has a feature to show the slowest tests:It would be nice if this list was available on a separate tab/page, with links ?
Example output of tool, after
make out/unittest.json
and "DONE 899 tests, 2 skipped in 13.313s"BTW: something is fishy here, go-test-report says 895 (not 899) "✓ Passed: 893 ‐ Skipped: 2 ✗ Failed: 0" ? --> filed Bug #19
So it shows all tests that ran slower than 100ms (slider?), sorted by duration...
Most of them run in "0s" (as they should), so this a nice way of finding culprits.
Web enhancements:
The text was updated successfully, but these errors were encountered: