Opened 4 years ago
Last modified 4 years ago
#32641 closed Cleanup/optimization
Log the number of tests found in DiscoverRunner.build_suite() — at Initial Version
Reported by: | Chris Jerdonek | Owned by: | nobody |
---|---|---|---|
Component: | Testing framework | Version: | dev |
Severity: | Normal | Keywords: | DiscoverRunner, build_suite |
Cc: | Triage Stage: | Ready for checkin | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | yes | UI/UX: | no |
Description
Currently, when running tests with DiscoverRunner
, the number of tests is displayed only at the very end of the test run.
However, knowing this number at the beginning of a test run could I think provide an increase in usability. For example, you'd be able to notice right away if a new test you're working was or wasn't included as expected, based on whether the number is the same or different from the previous run. Similarly, the early feedback would be helpful as a sanity check if you're trying to reduce the number of tests using different command-line options, and you're not sure if your invocation is correct.
Thus, I'd like to suggest that DiscoverRunner
display by default the number of tests discovered (and that match any filters) at the earliest point where this is known. This could be done inside DiscoverRunner.build_suite()
.
The code change could be as simple as:
diff --git a/django/test/runner.py b/django/test/runner.py index f187107157..c975ed92be 100644 --- a/django/test/runner.py +++ b/django/test/runner.py @@ -652,7 +652,8 @@ class DiscoverRunner: # _FailedTest objects include things like test modules that couldn't be # found or that couldn't be loaded due to syntax errors. test_types = (unittest.loader._FailedTest, *self.reorder_by) - all_tests = reorder_tests(all_tests, test_types, self.reverse) + all_tests = list(reorder_tests(all_tests, test_types, self.reverse)) + print('Found %d tests' % len(all_tests)) suite = self.test_suite(all_tests) if self.parallel > 1:
If there is any concern about adding an additional message, another possibility would be to display the current "Testing against Django installed in ..." message later in the test run, only after the number of tests is known, and include the test count in that message.