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
Depending on the size of the codebase, coverage report generation may take from sub-seconds to tens of minutes. For a test suite with sparse coverage (a lot of code, few tests), or selectively run tests, code coverage generation may take an order of magnitude longer than running the tests.
On a proprietary codebase I'm working on, a test run looks like the following:
-----8<-----
Time: 9.98 seconds, Memory: 140.26 MB
OK, but incomplete, skipped, or risky tests!
Tests: 2482, Assertions: 4214, Skipped: 24.
Generating code coverage report in HTML format ... done
Where it takes about 2 minutes between "Generating" and "done".
It would be nice if it looked like this:
Generating code coverage report in HTML format ... done (102 seconds taken).
The text was updated successfully, but these errors were encountered:
Depending on the size of the codebase, coverage report generation may take from sub-seconds to tens of minutes. For a test suite with sparse coverage (a lot of code, few tests), or selectively run tests, code coverage generation may take an order of magnitude longer than running the tests.
On a proprietary codebase I'm working on, a test run looks like the following:
Where it takes about 2 minutes between "Generating" and "done".
It would be nice if it looked like this:
The text was updated successfully, but these errors were encountered: