The k6 Cloud Test Script Recorder Chrome extension allows you to generate the bulk of your test scripts simply by browsing like a user would on your site or web app. The script created gives you a foundation which you can further edit, as required.
The k6 Cloud Chrome extension will capture everything – every single HTTP(s) request being loaded into the browser as you click – including ads, images, documents, etc., so you get a far more accurate read of what’s going on. Just press “record”, start browsing and when complete, the script will automatically upload to your k6 Cloud account.
The Chrome extension will not record other tabs or pop up windows. If you need to capture this information, you should check out converting from a HAR file.
Note: Before you begin, please be sure to force refresh the k6 Cloud app to ensure you are on the most recent version of the k6 Cloud app.
Download and install the k6 Browser Recorder.
Start a recording Open the extension by clicking the k6 logo, and press "Start recording" to begin recording the current browser tab. Now browse like a user would or how you want our Virtual Users to execute. We suggest basing this on real user behavior - don't try to visit every single page on your site or app. Focus on common journeys.
Save your test scripts Save the recorded script in any of your projects. If any third party requests or requests to download assets were made during the recording those requests will be filtered out by default. Would you want to include some of the requests in the third party list simply deselect the ones you want to include then hit save.
You can now edit your script as necessary. k6 Cloud's in app IDE will update in real time to alert you of any syntax errors. You may need to edit your script to deal with CSRF tokens, adding advanced business logic, creating custom metrics, etc.
Once done, press run to start your test
- The default configuration will be a 12 minute test that ramps to 10 Virtual Users over 1 minute, stays at 10 for 10 minutes, then ramps back to 0 over 1 minute. You can change this in the stages section of the script. Refer to this article for more information on ramping configurations.
- No load zone is specified and it will run out of Ashburn by default. You can specify different load zones by adding a
ext.loadimpact.distributionoption. See this article for more information
- We have set
discardResponseBodies: true. This will discard all response bodies by default.