Mock APIs | Playwright
Introduction| playwright.dev
The [WebSocket] class represents WebSocket connections within a page. It provides the ability to inspect and manipulate the data being transmitted and received.| playwright.dev
[Response] class represents responses which are received by page.| playwright.dev
Whenever the page sends a request for a network resource the following sequence of events are emitted by [Page]:| playwright.dev
Whenever a network route is set up with page.route() or browserContext.route(), the Route object allows to handle the route.| playwright.dev
This API is used for the Web API testing. You can use it to trigger API endpoints, configure micro-services, prepare environment or the service to your e2e test.| playwright.dev
A Browser is created via browserType.launch(). An example of using a [Browser] to create a [Page]:| playwright.dev
Page provides methods to interact with a single tab in a Browser], or an [extension background page in Chromium. One [Browser] instance might have multiple [Page] instances.| playwright.dev
BrowserContexts provide a way to operate multiple independent browser sessions.| playwright.dev
The WebSocket API makes it possible to open a two-way interactive communication session between the user's browser and a server. With this API, you can send messages to a server and receive responses without having to poll the server for a reply.| MDN Web Docs
XMLHttpRequest (XHR) objects are used to interact with servers. You can retrieve data from a URL without having to do a full page refresh. This enables a Web page to update just part of a page without disrupting what the user is doing.| MDN Web Docs
