fixup

HeahDude · HeahDude · commit f43527bd19dd · 2020-04-17T18:37:17.000+02:00
diff --git a/form/unit_testing.rst b/form/unit_testing.rst
@@ -125,8 +125,18 @@ variable exists and will be available in your form themes::
     Use :ref:`PHPUnit data providers <testing-data-providers>` to test multiple
     form conditions using the same test code.
 
-Testings Types from the Service Container
------------------------------------------
+.. caution::
+
+    When your type relies on the ``EntityType``, you should register the
+    :class:`Symfony\\Bridge\\Doctrine\\Form\\DoctrineOrmExtension`, which will
+    need to mock the ``ManagerRegistry``.
+
+    However, If you cannot use a mock to write your test, you should extend
+    the ``KernelTestCase`` instead and use the ``form.factory`` service to
+    create the form.
+
+Testings Types Registered as Services
+-------------------------------------
 
 Your form may be used as a service, as it depends on other services (e.g. the
 Doctrine entity manager). In these cases, using the above code won't work, as
@@ -228,14 +238,6 @@ allows you to return a list of extensions to register::
     registered in tests. You can find other extensions from the Form component
     in the ``Symfony\Component\Form\Extension`` namespace.
 
-.. caution::
-
-    When your type relies on the ``EntityType``, you should register the
-    :class:`Symfony\\Bridge\\Doctrine\\Form\\DoctrineOrmExtension`, which will
-    need to mock the ``ManagerRegistry``. If you cannot use a mock to write
-    your test, you should extend the ``KernelTestCase`` instead and use the
-    form factory as a service by fetching it from the container.
-
 It is also possible to load custom form types, form type extensions or type
 guessers using the :method:`Symfony\\Component\\Form\\Test\\FormIntegrationTestCase::getTypes`,
 :method:`Symfony\\Component\\Form\\Test\\FormIntegrationTestCase::getTypeExtensions`
