From 8c2319168a935003527fa468dae59771abbffa42 Mon Sep 17 00:00:00 2001 From: Bruno Oliveira Date: Fri, 28 Jul 2017 23:15:59 -0300 Subject: [PATCH] Rephrase the bit about unittest migration to pytest --- doc/en/unittest.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/en/unittest.rst b/doc/en/unittest.rst index b177bf861..56721ff9b 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 gradually move away from subclassing from ``unittest.TestCase`` - to *plain asserts* and the benefits from the full pytest feature set. + You can also gradually move away from subclassing from ``unittest.TestCase`` to *plain asserts* + and then start to benefit from the full pytest feature set step by step.