# UserLimit documentation

> Managed real-browser scenario testing. Source is converted into supported actions, not executed as an arbitrary Playwright program.

Read individual articles for focused questions, or fetch the complete documentation for full context.

## Documentation

- [Documentation home](https://userlimit.com/documentation/index.md)
- [Complete documentation](https://userlimit.com/documentation.md): All public articles in one Markdown document.
- [What UserLimit tests](https://userlimit.com/documentation/get-started/overview.md): UserLimit runs browser scenarios under load to show how a website behaves as traffic increases, and what a report can and cannot establish.
- [Run your first load test](https://userlimit.com/documentation/get-started/first-load-test.md): This guide covers a first load test: a verified domain, a read-only scenario, a small workload and the resulting report.
- [Verify a domain](https://userlimit.com/documentation/get-started/verify-domain.md): Domain verification confirms that you control a hostname before it can be used in a scenario. Permission to test connected third-party services is separate.
- [Sessions, arrivals and concurrency](https://userlimit.com/documentation/concepts/sessions-and-concurrency.md): 600 sessions over ten minutes does not mean 600 simultaneous users. How sessions, arrival rate and concurrency relate, and how to estimate concurrency.
- [Create and import a scenario](https://userlimit.com/documentation/journeys/create-and-import.md): A scenario is a saved sequence of browser actions that represents how a visitor uses your website. Paste a Playwright script or set one up by hand.
- [Validate and fix a scenario](https://userlimit.com/documentation/journeys/validate.md): Validation runs one browser session through the saved actions to check whether the scenario can execute.
- [Configure traffic and test settings](https://userlimit.com/documentation/runs/configure-traffic.md): Traffic settings control how many sessions start, when they start and where they run. Choose a traffic shape and estimate usage before a run.
- [Start, stop and monitor a run](https://userlimit.com/documentation/runs/lifecycle.md): A run starts browser sessions and collects their results in a report. Sessions can continue after the configured arrival window ends.
- [Read a load-test report](https://userlimit.com/documentation/results/read-a-report.md): A report shows recorded session outcomes, failures, timings and usage for a run. This guide explains how to interpret them.
- [Test a storefront browsing scenario](https://userlimit.com/documentation/recipes/storefront.md): Can visitors reach the relevant product pages under the expected browsing workload? This recipe answers that question without placing orders.
- [Test campaign and launch readiness](https://userlimit.com/documentation/recipes/launch-readiness.md): A sequence of comparable runs can help assess whether a scenario meets the performance targets for a launch.
- [Write a client-facing test summary](https://userlimit.com/documentation/recipes/client-summary.md): A client summary connects the test results to a business question, with enough context to explain the findings and their limits.
- [Playwright compatibility and conversion](https://userlimit.com/documentation/reference/playwright-compatibility.md): UserLimit converts a script into saved steps. A script importing successfully does not mean it will behave exactly as it does in Playwright.
- [Metrics and measurement](https://userlimit.com/documentation/reference/metrics.md): Each metric describes a particular set of sessions, actions or requests. Failures and missing measurements help put the timings in context.
- [Usage and billing](https://userlimit.com/documentation/reference/usage-and-billing.md): Usage is the total time used by all sessions in a run. One hour of elapsed test time is not the same as one Virtual-User hour.
- [Troubleshoot a failed or misleading test](https://userlimit.com/documentation/help/troubleshooting.md): This guide explains how to investigate common problems with domain verification, scripts, session execution, results and notifications.
- [Test production safely](https://userlimit.com/documentation/help/production-safety.md): Production tests can affect visitors and connected services. Permission, site monitoring and a way to stop the run help manage that impact.
- [Contact support](https://userlimit.com/documentation/support.md): Support can help with scenario failures, test results, account capacity and billing questions. Run and scenario identifiers help us find the issue quickly.