minor #9974 [testing] tell about self::$container (nicolas-grekas)

javiereguiluz · javiereguiluz · commit 84fb4736c3a7 · 2018-06-29T08:56:10.000+02:00
This PR was merged into the 4.1 branch. Discussion ---------- [testing] tell about self::$container Fixes #9455. Same as https://symfony.com/blog/new-in-symfony-4-1-simpler-service-testing Commits ------- e64d89d [testing] tell about self::$container
diff --git a/testing.rst b/testing.rst
@@ -508,18 +508,30 @@ You can also get the objects related to the latest request::
 Accessing the Container
 ~~~~~~~~~~~~~~~~~~~~~~~
 
+.. versionadded:: 4.1
+
+    The ``self::$container`` property was introduced in Symfony 4.1.
+
 It's highly recommended that a functional test only tests the response. But
 under certain very rare circumstances, you might want to access some internal
-objects to write assertions. In such cases, you can access the Dependency
-Injection Container::
+objects to write assertions. In such cases, you can access your services via
+a special property on the test class. Because services are private by default,
+this property holds a special container, which allows fetching public and all
+non-removed private services::
 
-    // will be the same container used in your test, unless you're using
+    // gives access to the same services used in your test, unless you're using
     // $client->insulate() or using real HTTP requests to test your application
-    $container = $client->getContainer();
+    $container = self::$container;
 
 For a list of services available in your application, use the ``debug:container``
 command.
 
+.. tip::
+
+    The special container that gives access to private services exists only in
+    the ``test`` environment and is itself a service that you can accessed from
+    the real container using the ``test.service_container`` id.
+
 .. tip::
 
     If the information you need to check is available from the profiler, use
