diff options
| author | Bruno Oliveira <nicoddemus@gmail.com> | 2017-07-28 07:55:34 -0300 |
|---|---|---|
| committer | Bruno Oliveira <nicoddemus@gmail.com> | 2017-07-28 07:55:34 -0300 |
| commit | 7082320f3f69e0fac9f2f80f0af6a1ac463411af (patch) | |
| tree | 698503cfaefda34817cf3c26e84bed5f4ffdfa60 /doc/en/unittest.rst | |
| parent | 6fe7069cbb4c23b6800afff692e0162e000d55e9 (diff) | |
| download | pytest-7082320f3f69e0fac9f2f80f0af6a1ac463411af.tar.gz | |
Apply modifications requested in review
Diffstat (limited to 'doc/en/unittest.rst')
| -rw-r--r-- | doc/en/unittest.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/en/unittest.rst b/doc/en/unittest.rst index e2ebe3e38..b177bf861 100644 --- a/doc/en/unittest.rst +++ b/doc/en/unittest.rst @@ -198,5 +198,5 @@ was executed ahead of the ``test_method``. The above ``usefixtures`` and ``autouse`` examples should help to mix in pytest fixtures into unittest suites. - You can also consider incrementally leave away ``unittest.TestCase`` subclassing, - using plain asserts and get the full pytest feature set. + You can also gradually move away from subclassing from ``unittest.TestCase`` + to *plain asserts* and the benefits from the full pytest feature set. |