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
{{ message }}
This repository has been archived by the owner on Apr 29, 2021. It is now read-only.
It would be really useful to get the test run time along with the result when running the tests, that will allow easier check of which tests are taking most of the time and ease building faster tests
The text was updated successfully, but these errors were encountered:
I'd love to see this feature built-in as well. In the meantime, we've instrumented the dokku test suite thusly. It's obviously not the same as per test timing but it at least shows us how long each bats file takes.
I like this idea also, it would be helpful to measure which case kills the cpu and know I have to turn back to the wrapped command and do manual profiling by time command
It would be really useful to get the test run time along with the result when running the tests, that will allow easier check of which tests are taking most of the time and ease building faster tests
The text was updated successfully, but these errors were encountered: