Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Added helper to test.support for parameterizing tests #135120

Open
Labels
3.13bugs and security fixes3.14bugs and security fixes3.15new features, bugs and security fixespendingThe issue will be closed if no feedback is providedtestsTests in the Lib/test dirtype-featureA feature request or enhancement
@serhiy-storchaka

Description

@serhiy-storchaka

This is a simple decorator modeled afterpytest.mark.parametrize. It allows to "parametrize" tests, each parametrized test is run as a subtest.

The decorator specifies the name(s) of parameters (as an iterable or a comma separated string) and their values (an iterable of values for parameters):

@subTests('a,b', [('foo',2), ('bar',5)])deftest_foo(self,a,b):    ...

is equivalent to

deftest_foo(self):fora,bin [('foo',2), ('bar',5)]:withself.subTest(a=a,b=b):            ...

It allows to save 2 levels of indentation.

Multiple decorators can be used, this generates a Descartes production of parameter values:

@subTests('a,b', [('foo',2), ('bar',5)])@subTests('c',range(5))deftest_foo(self,a,b,c):    ...

is equivalent to

deftest_foo(self):fora,bin [('foo',2), ('bar',5)]:withself.subTest(a=a,b=b):forcinrange(5):withself.subTest(c=c):                    ...

It allows to save even more 2 levels of indentation.

It has also optional keyword-only parameter_do_cleanups._do_cleanups=True tells to calldoCleanups() after each subtest. This is temporary feature, only for use in test_ntpath. In general, it is wrong to do this becausedoCleanups() will also calls callbacks added insetUp. It will be replaced either byaddSubTestCleanup() (seehttps://discuss.python.org/t/unittest-add-addcleanup-to-subtest/91827 and#134079) or by other methods (for example by adding fences for cleanup). Also, it will not be needed for real test parameterization.

There are differences from "real" parameterization:

  • setUp andtearDown are only run once, before and after all subtests.
  • It is impossible to select or filter out tests with specific parameters.
  • It can only parametrize test methods, not classes.

I plan to implement real parameterization, this is why I only propose to add that decorator intest.support, not inunittest. In any case it would be backported intest.support. We may finally add both decorators inunittest if this does not create confusion.

The namesubTests is intentionally chosen to not confuse withparametrize which is reserved for real test parameterization.

The PR contains also several examples of using that decorator.

Linked PRs

Metadata

Metadata

Assignees

No one assigned

    Labels

    3.13bugs and security fixes3.14bugs and security fixes3.15new features, bugs and security fixespendingThe issue will be closed if no feedback is providedtestsTests in the Lib/test dirtype-featureA feature request or enhancement

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions


      [8]ページ先頭

      ©2009-2025 Movatter.jp