While we intend to keep experimental modules as stable as possible, we may need to introduce breaking changes. This could happen at future k6 releases until the module becomes fully stable and graduates as a k6 core module. For more information, refer to the extension graduation process.
Experimental modules maintain a high level of stability and follow regular maintenance and security measures. Feel free to open an issue if you have any feedback or suggestions.
The browser module APIs aim for rough compatibility with the Playwright API for NodeJS.
Note that because k6 does not run in NodeJS, the browser module APIs will slightly differ from their Playwright counterparts.
To work with the browser module, make sure you are using the latest k6 version.
The table below lists the properties you can import from the browser module ('k6/experimental/browser').
|The browser module API is the entry point for all your tests. See the example and the API below.
|Returns predefined emulation settings for many end-user devices that can be used to simulate browser behavior on a mobile device. See the devices example below.
The browser module is the entry point for all your tests, and it is what interacts with the actual web browser via Chrome DevTools Protocol (CDP). It manages:
- BrowserContext which is where you can set a variety of attributes to control the behavior of pages;
- and Page which is where your rendered site is displayed.
|Returns the current BrowserContext.
|Indicates whether the CDP connection to the browser process is active or not.
|Creates and returns a new BrowserContext.
|Creates a new Page in a new BrowserContext and returns the page. Pages that have been opened ought to be closed using Page.close. Pages left open could potentially distort the results of Web Vital metrics.
|Returns the browser application's version.
Then, you can run the test with this command. Also, see the browser module options for customizing the browser module's behavior using environment variables.
|Enables independent browser sessions with separate Pages, cache, and cookies.
|Represents an in-page DOM element.
|Access and interact with the Page.'s Frames.
|Used to simulate the keyboard interactions with the associated Page.
|The Locator API makes it easier to work with dynamically changing elements.
|Used to simulate the mouse interactions with the associated Page.
|Provides methods to interact with a single tab in a browser.
|Used to keep track of the request the Page makes.
|Represents the response received by the Page.
|Used to simulate touch interactions with the associated Page.
|Represents a WebWorker.
You can customize the behavior of the browser module by providing browser options as environment variables.
|Extra command line arguments to include when launching browser process. See this link for a list of Chromium arguments. Note that arguments should not start with -- (see the example).
|All CDP messages and internal fine grained logs will be logged if set to true.
|Override search for browser executable in favor of specified absolute path.
|Show browser GUI or not. true by default.
|Ignore any of the default arguments included when launching a browser process.
|Default timeout to use for various actions and navigation. '30s' if not set.
The following command passes the browser module options as environment variables to launch a headful browser with custom arguments.
List of default arguments included when launching the browser process. You can pass one or more of the arguments to the K6_BROWSER_IGNORE_DEFAULT_ARGS environment variable when starting a test for the ones you want to ignore.
The starting '--' have been omitted from the argument names in these lists.
|Disables several subsystems which run network requests in the background. This is used during network performance testing to avoid measurement noise.
|Comma-separated list of feature names to enable.
|Disables task throttling of timer tasks from background pages.
|Disables backgrounding renders for occluded windows. Done for tests to avoid nondeterministic behavior.
|Disables the crash reporting.
|Disables default component extensions with background pages. Useful for performance tests where these pages may interfere with results.
|Disables the installation of default apps on the first run. This is used during automated testing.
|The /dev/shm partition is too small in certain VM environments, causing Chrome to fail or crash. This flag provides a work-around for this issue (a temporary directory will always be used to create anonymous shared memory files).
|Comma-separated list of feature names to disable.
|Suppresses hang monitor dialogs in renderer processes. This may allow slow unload handlers on a page to prevent the tab from closing, but the Task Manager can be used to terminate the offending process in this case.
|Disables pop-up blocking.
|Usually, when the user attempts to navigate to a page that was the result of a post request, the browser prompts to make sure that's the intention of the user. This switch may be used to disable that check during automated testing.
|Prevents renderer process backgrounding when set.
|Forces all monitors to be treated as though they have the specified color profile. Accepted values are "srgb" and "generic-rgb" (currently used by Mac layout tests) and "color-spin-gamma24" (used by layout tests).
|Enables the recording of metrics reports but disables reporting. This executes all the code that a normal client would use for reporting, except the report is dropped rather than sent to the server. This is useful for finding issues in the metrics code during UI and performance tests.
|Skips the "First Run" tasks, whether or not it's the first run, and the "What's New" page. This does not drop the "First Run" sentinel and thus doesn't prevent "First Run" from occurring the next time Chromium is launched without this flag. It also does not update the last "What's New" milestone, so it does not prevent "What's New" from occurring the next time Chromium is launched without this flag.
|Enables indication that the browser is controlled by automation.
|Specifies which encryption storage backend to use. The possible values are kwallet, kwallet5, gnome, gnome-keyring, gnome-libsecret, and basic. Any other value will lead to Chromium detecting the best backend automatically.
|Uses mock keychain on Mac to prevent the blocking permissions dialog about: "Chrome wants to use your confidential information stored in your keychain."
|Disables the service process from adding itself as an autorun process. This does not delete existing autorun registrations, it just prevents the service from registering a new one.
|Does not automatically open a browser window on startup (used when launching Chrome for the purpose of hosting background apps).
|Disables the default browser check. Useful for UI/browser tests where we want to avoid having the default browser info-bar displayed.
|Run in headless mode, i.e., without a UI or display server dependencies. Set by K6_BROWSER_HEADLESS environment variable (default true).
|Sets the initial window size. Provided as string in the format "800,600".
Additionally if headless mode is set to true in browser options, the following arguments are also set:
|Prevents creating scrollbars for web content. Useful for taking consistent screenshots.
|Mutes audio sent to the audio device so it is not audible during automated testing.
|Sets blink settings. Format is <name>[=<value>],<name>[=<value>],... The names are declared in settings.json5 from chromium project. For boolean type, use "true", "false", or omit '=<value>' part to set to true. For enum type, use the int value of the enum value.
To emulate the browser behaviour on a mobile device and approximately measure the browser performance, you can import devices from k6/experimental/browser.