Follow along to learn how to:
- Run a test
- Interact with elements on your webpage
- Wait for page navigation
- Run both browser-level and protocol-level tests in a single script
- Run xk6-browser tests in a Docker container
With these example snippets, you'll run the test locally with your machine's resources. xk6-browser is not available within k6 cloud as of yet.
To run a simple local script:
Follow the Installation Guidelines and make sure there is a binary named xk6-browser in your current working directory.
Copy the following code, paste it into your favorite editor, and save it as script.js:script.js
The preceding code imports the chromium BrowserType (currently the only available BrowserType implementation), and uses its launch method to start up a Chromium Browser process. After it starts, you can interact with it using the browser-level APIs. This example visits a test URL, waits until the network is idle and takes a screenshot of the page. Afterwards, it closes the page and the browser.note
To provide rough compatibility with the Playwright API, the xk6-browser API is also being converted from synchronous to asynchronous. page.goto() is now asynchronous so .then() is used to deal with the asynchronous nature of the operation.
Then, run xk6-browser on your terminal with this command:CLInote
The ./ prefix tells your shell to run the binary located in the current working directory. This is required on macOS and Linux, but not on the Windows cmd.exe shell. On PowerShell, specify .\xk6-browser instead.
If you installed xk6-browser with a system package, or placed the binary in a directory that's part of your $PATH environment variable, you can omit the ./ or .\ prefixes.
You can use page.locator() and pass in the element's selector you want to find on the page. page.locator() will create and return a Locator object, which you can later use to interact with the element.
To find out which selectors xk6-browser supports, check out Selecting Elements.
You can also use page.$() instead of page.locator(). You can find the differences between page.locator() and page.$ in the Locator API documentation.
The preceding code creates and returns a Locator object with the selectors for both login and password passed as arguments.
Within the Locator API, various methods such as type() can be used to interact with the elements. The type() method types a text to an input field.
As explained previously, the k6 API is synchronous. However, since many browser operations happen asynchronously, and in order to follow the Playwright API more closely, we are working on migrating most xk6-browser methods to be asynchronous as well.
To avoid timing errors or other race conditions in your script, if you have actions that load up a different page, you need to make sure that you wait for that action to finish before continuing.
The preceding code uses Promise.all() to wait for the two promises to be resolved before continuing. Since clicking the submit button causes page navigation, page.waitForNavigation() is needed because the page won't be ready until the navigation completes. This is required because there can be a race condition if these two actions don't happen simultaneously.
Then, you can use check from the k6 API to assert the text content of a specific element. Finally, you close the page and the browser.
The real power of xk6-browser shines when it’s combined with the existing features of k6. A common scenario that you can try is to mix a smaller subset of browser-level tests with a larger protocol-level test which can simulate how your website responds to various performance events.
To run a browser-level and protocol-level test concurrently, you can use scenarios.
Keep in mind that there is an additional performance overhead when it comes to spinning up a browser VU and that the resource usage will depend on the system under test.
The preceding code contains two scenarios. One for the browser-level test called browser and one for the protocol-level test called news. Both scenarios are using the constant-vus executor which introduces a constant number of virtual users to execute as many iterations as possible for a specified amount of time.
Since it's all in one script, this allows for greater collaboration amongst teams.
To run the test, use the following command and replace script.js with your file.