PlaywrightKernelClient

Playwright\Symfony\Client\PlaywrightKernelClient

BrowserKit client that intercepts browser requests and routes them through Symfony's HttpKernel.
This is the core client for in-process E2E testing of Symfony applications. It combines a real
Playwright browser with Symfony's HttpKernel to enable full browser testing while maintaining
access to Symfony internals (services, events, profiler, request/response inspection).
Primary role in architecture:
- Returned by PlaywrightTestCase client factories
- Intercepts HTTP requests from the browser to configured hosts (localhost, 127.0.0.1)
- Routes intercepted requests through Symfony's kernel in the same PHP process
- Provides access to last Symfony request/response for assertions
- Integrates AssetServer for fast static asset serving (bypasses kernel)
How request interception works:
1. User calls visit('/path') → navigates browser to http://localhost/path
2. Browser makes HTTP request → intercepted via BrowserSessionInterface->setupRouting()
3. Request matched against interceptedHosts → if matched, proceeds to step 4
4. AssetServer checks if request is for static asset → if yes, serves directly
5. Otherwise: RequestConverter → HttpKernel->handle() → Kernel->terminate() → ResponseConverter → browser
6. Test can inspect via getLastSymfonyRequest(), getLastSymfonyResponse()
Key features:
- In-process kernel execution (no real HTTP, no separate server)
- Full access to Symfony container, services, and profiler
- beforeRequest() and afterResponse() hooks for custom logic
- Cookie management and authentication helpers
- BrowserKit API compatibility (visit, click, submit, getCrawler)
When to use:
- Testing your Symfony application with real browser behavior
- Need to inspect Symfony internals (request, response, services)
- Want fast E2E tests without network overhead
When NOT to use:
- Testing external websites → use BrowserKit\PlaywrightClient instead
- Need real HTTP networking behavior → use BrowserKit\PlaywrightClient instead