Load Testing with Playwright

Dotcom-Monitor supports importing Playwright for .NET tests into Loadview for Playwright load testing. Use existing Playwright tests to simulate browser-based user journeys under load and evaluate application performance as the number of concurrent users increases.

How Playwright Load Testing Works

Unlike protocol-based load tests, which generate requests directly, Playwright load tests execute browser-based workflows. This makes them useful for evaluating complete user journeys that depend on JavaScript execution, page rendering, authentication, and interactive elements.

Playwright tests can reproduce user interactions such as logging in, navigating between pages, submitting forms, and interacting with dynamic content.

Note that browser-based testing generally requires more resources per virtual user than protocol-based testing. To choose the right testing approach and use browser-based testing efficiently, see Playwright Load Testing: How to Simulate Real Users at Scale.

Import a Playwright Test

Before importing a Playwright test, verify that it is written using Playwright for .NET and runs successfully in your local development environment.

To import a Playwright test into LoadView:

1. In LoadView, create a new test with the Playwright target type.
2. Import your Playwright test.
3. Review the imported script and update environment-specific values, such as URLs, credentials, variables, or validations, if necessary.
4. Set Flag as Error Responses That Exceed Value. This setting specifies the maximum time, in seconds, that the system will wait for a response from the target resource. If the response is not received within the specified time, the system flags it as an error.
5. Configure DNS options, as required.
6. Save the device.

After importing the test, review the script, configure the load test settings, and run the test using LoadView’s distributed load testing infrastructure, with locations available in more than 30 geographic regions.