File tree Expand file tree Collapse file tree 1 file changed +4
-4
lines changed Expand file tree Collapse file tree 1 file changed +4
-4
lines changed Original file line number Diff line number Diff line change @@ -246,7 +246,7 @@ Retrieving Services in the Test
246
246
247
247
In your integration tests, you often need to fetch the service from the
248
248
service container to call a specific method. After booting the kernel,
249
- the container is stored in ``self::$container ``::
249
+ the container is stored in ``static::getContainer() ``::
250
250
251
251
// tests/Service/NewsletterGeneratorTest.php
252
252
namespace App\Tests\Service;
@@ -261,8 +261,8 @@ the container is stored in ``self::$container``::
261
261
// (1) boot the Symfony kernel
262
262
self::bootKernel();
263
263
264
- // (2) use self::$container to access the service container
265
- $container = self::$container ;
264
+ // (2) use static::getContainer() to access the service container
265
+ $container = static::getContainer() ;
266
266
267
267
// (3) run some service & test the result
268
268
$newsletterGenerator = $container->get(NewsletterGenerator::class);
@@ -272,7 +272,7 @@ the container is stored in ``self::$container``::
272
272
}
273
273
}
274
274
275
- The container in ``self::$container `` is actually a special test container.
275
+ The container in ``static::getContainer() `` is actually a special test container.
276
276
It gives you access to both the public services and the non-removed
277
277
:ref: `private services <container-public >` services.
278
278
You can’t perform that action at this time.
0 commit comments