bpo-45229: Remove test_main in many tests#28405
Conversation
Sorry, something went wrong.
serhiy-storchaka
added
tests
Tests in the Lib/test dir
DO-NOT-MERGE
needs backport to 3.9
needs backport to 3.10
only security fixes
labels
Sep 17, 2021
serhiy-storchaka
force-pushed
the
regrtest-no-test-main
branch
2 times, most recently
from
c22388d to
a4083e6
Compare
September 17, 2021 07:41
Instead of explicitly enumerate test classes for run_unittest() use the unittest ability to discover tests. This also makes these tests discoverable and runnable with unittest. load_tests() can be used for dynamic generating tests and adding doctests. setUpModule(), tearDownModule() and addModuleCleanup() can be used for running code before and after all module tests.
serhiy-storchaka
force-pushed
the
regrtest-no-test-main
branch
from
a4083e6 to
dba9b2f
Compare
September 17, 2021 12:49
serhiy-storchaka
requested review from
a team,
brettcannon,
encukou,
ericsnowcurrently,
ncoghlan,
vsajip and
warsaw
as code owners
September 17, 2021 12:49
serhiy-storchaka
added
🔨 test-with-buildbots
Test PR w/ buildbots; report in status section
and removed
DO-NOT-MERGE
labels
Sep 17, 2021
|
🤖 New build scheduled with the buildbot fleet by @serhiy-storchaka for commit dba9b2f 🤖 If you want to schedule another build, you need to add the ":hammer: test-with-buildbots" label again. |
Sorry, something went wrong.
bedevere-bot
removed
the
🔨 test-with-buildbots
Test PR w/ buildbots; report in status section
label
Sep 17, 2021
|
Thanks @serhiy-storchaka for the PR 🌮🎉.. I'm working now to backport this PR to: 3.9, 3.10. |
Sorry, something went wrong.
|
Sorry, @serhiy-storchaka, I could not cleanly backport this to |
Sorry, something went wrong.
|
Sorry @serhiy-storchaka, I had trouble checking out the |
Sorry, something went wrong.
Instead of explicitly enumerate test classes for run_unittest() use the unittest ability to discover tests. This also makes these tests discoverable and runnable with unittest. load_tests() can be used for dynamic generating tests and adding doctests. setUpModule(), tearDownModule() and addModuleCleanup() can be used for running code before and after all module tests.. (cherry picked from commit 40348ac) Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
Instead of explicitly enumerate test classes for run_unittest() use the unittest ability to discover tests. This also makes these tests discoverable and runnable with unittest. load_tests() can be used for dynamic generating tests and adding doctests. setUpModule(), tearDownModule() and addModuleCleanup() can be used for running code before and after all module tests.. (cherry picked from commit 40348ac) Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
Instead of explicitly enumerate test classes for run_unittest() use the unittest ability to discover tests. This also makes these tests discoverable and runnable with unittest. load_tests() can be used for dynamic generating tests and adding doctests. setUpModule(), tearDownModule() and addModuleCleanup() can be used for running code before and after all module tests. (cherry picked from commit 40348ac)
Instead of explicitly enumerate test classes for run_unittest() use the unittest ability to discover tests. This also makes these tests discoverable and runnable with unittest. load_tests() can be used for dynamic generating tests and adding doctests. setUpModule(), tearDownModule() and addModuleCleanup() can be used for running code before and after all module tests.. (cherry picked from commit 40348ac)
Instead of explicitly enumerate test classes for run_unittest() use the unittest ability to discover tests. This also makes these tests discoverable and runnable with unittest. load_tests() can be used for dynamic generating tests and adding doctests. setUpModule(), tearDownModule() and addModuleCleanup() can be used for running code before and after all module tests.
Reviewers
4 participants
Instead of explicitly enumerate test classes for run_unittest()
use the unittest ability to discover tests. This also makes these
tests discoverable and runnable with unittest.
load_tests() can be used for dynamic generating tests and adding
doctests. setUpModule(), tearDownModule() and addModuleCleanup()
can be used for running code before and after all module tests.
https://bugs.python.org/issue45229