Skip to content

Commit f79938e

Browse files
committed
docs: add k6 version for the browser module
1 parent af3ea85 commit f79938e

File tree

2 files changed

+12
-0
lines changed

2 files changed

+12
-0
lines changed

src/data/markdown/docs/02 javascript api/07 k6-experimental/01 browser.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,12 @@ The browser module APIs aim for rough compatibility with the [Playwright API for
99

1010
Note that because k6 does not run in NodeJS, the browser module APIs will slightly differ from their Playwright counterparts.
1111

12+
<Blockquote mod="note" title="">
13+
14+
To work with the browser module, make sure you are using [k6 version 0.43.0](https://github.com/grafana/k6/releases/tag/v0.43.0) or above.
15+
16+
</Blockquote>
17+
1218
## Modules
1319

1420
The table below lists the importable properties from the top level module (`'k6/experimental/browser'`).

src/data/markdown/translated-guides/en/03 Using k6 browser/01 Overview.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,12 @@ The [Browser module](https://github.com/grafana/xk6-browser) brings browser auto
1111

1212
This module aims to provide rough compatibility with the Playwright API, so you don’t need to learn a completely new API.
1313

14+
<Blockquote mod="note" title="">
15+
16+
To work with the browser module, make sure you are using [k6 version 0.43.0](https://github.com/grafana/k6/releases/tag/v0.43.0) or above.
17+
18+
</Blockquote>
19+
1420
## Use case for browser testing
1521

1622
The main use case for the browser module is to test performance on the browser level. Browser-level testing provides a way to measure user experience and find issues that are difficult to catch on the protocol level. Browser-level testing can help you answer questions like:

0 commit comments

Comments
 (0)