This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author serhiy.storchaka
Recipients serhiy.storchaka
Date 2021-09-17.07:31:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1631863872.14.0.108756439349.issue45229@roundup.psfhosted.org>
In-reply-to
Content
Currently regrtest supports two ways of collecting and running tests in module.

1. If the module contains the "test_main" function, regrtest just calls it. This function usually calls run_unittest() with a list of test classes, composed manually, it can also run doctests with run_doctest(), generate list of test classes dynamically, and run some code before and after running tests.

2. Otherwise regrtest uses unittest for for collecting tests.

The disadvantage of the former way is that new test classes should be added manually to the list. If you forget to do this, new tests will not be run. See for example issue45185 and issue45187. Not runned tests can hide bugs.

So it would be better to eliminate human factor and detect tests automatically.
History
Date User Action Args
2021-09-17 07:31:12serhiy.storchakasetrecipients: + serhiy.storchaka
2021-09-17 07:31:12serhiy.storchakasetmessageid: <1631863872.14.0.108756439349.issue45229@roundup.psfhosted.org>
2021-09-17 07:31:12serhiy.storchakalinkissue45229 messages
2021-09-17 07:31:11serhiy.storchakacreate