Browser automation and end-to-end web testing for k6
An extension for k6 adding browser-level APIs with rough Playwright compatibility.
Download ·
Install ·
Documentation ·
Community Forum
xk6-browser is a k6 extension that supports browser automation through the Chrome Devtools Protocol (CDP). It adds browser-level APIs to interact with browsers and collect frontend performance metrics as part of your k6 tests.
https://user-images.githubusercontent.com/10811379/200350050-f346931f-6402-487e-bf4d-eff808ac2190.mp4
Special acknowledgment to the authors of Playwright and Puppeteer for their trailblazing work in this area. This project is heavily influenced and in some regards based on the code of those projects.
Goals
- Bring browser automation to the k6 testing platform while supporting core k6 features like VU executors, scenarios, metrics, checks, thresholds, logging, DNS remapping, IP blocklists, etc.
- Test stability as the top priority by supporting non-flaky selectors combined with auto-waiting for actions just like Playwright.
- Aim for rough API compatibility with Playwright. The reason for this is two-fold; for one we don't want users to have to learn a completely new API just to use xk6-browser, and secondly, it opens up for using the Playwright RPC server as an optional backend for xk6-browser should we decide to support that in the future.
- Support for Chromium compatible browsers first, and eventually Firefox and WebKit-based browsers.
See our project roadmap for more details.
Get started
Documentation
Get help
- If you're having issues installing or running xk6-browser, refer to TROUBLESHOOTING.
- To get help about usage, report bugs, suggest features, and discuss xk6-browser with other users see SUPPORT.md.
- Community discussion happens at the xk6-browser forum.
Additional resources
To find out more about xk6-browser or browser testing in general, check out the following links.
Note: since our API is still transitioning, some of the code snippets from the links below might be inaccurate, though the concepts should still be correct. For the latest, refer to our up-to-date API documentation.