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
With these example snippets, you'll run the test locally with your machine's resources. The browser module is not available within k6 cloud as of yet.
To run a simple local script:
- Copy the following code, paste it into your favorite editor, and save it as script.js:
The preceding code imports the browser (the browser module), and uses its newPage method to open a new page.
After getting the page, you can interact with it using the Page methods. This example visits a test URL and takes a screenshot of the page.
Subsequently, the page is closed. This allows for the freeing up of allocated resources and enables the accurate calculation of Web Vital metrics.
To provide rough compatibility with the Playwright API, the browser module API is also being converted from synchronous to asynchronous. page.goto() is now asynchronous so await keyword is used to deal with the asynchronous nature of the operation.
- Then, run the test on your terminal with this command:
You can also use the browser module options to customize the launching of a browser process. For instance, you can start a headful browser using the previous test script with this command.
When using Docker to run k6 browser tests, make sure you have pulled the correct image with Chromium built-in. See k6 Installation via Docker for more information.
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 the browser module 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.
Since many browser operations happen asynchronously, and to follow the Playwright API more closely, we are working on migrating most of the browser module 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 the browser module 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. This approach is what we refer to as hybrid load testing and provides advantages such as:
- testing real user flows on the frontend while generating a higher load in the backend
- measuring backend and frontend performance in the same test execution
- increased collaboration between backend and frontend teams since the same tool can be used
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.