Test Runners
WebdriverIO
Because Replay Browser lets you record anything that happens inside it, you can simply just point your test script to the Replay Browser binary and you are all set up.
Install Replay package
To start, you need to install replayio
package to your project.
Terminal
npm i replayio
Set up the browser binary
In order to use Replay Browser in your WebdriverIO scripts, you need to point your configuration to the Replay Browser binary. The getBrowserPath
function will take care of locating the binary on your machine.
wdio.config.js
1import { getBrowserPath } from 'replayio'23const chromiumPath = getBrowserPath()45exports.config = {6 specs: ['./test/*.js'],7 automationProtocol: 'devtools',8 capabilities: [9 {10 maxInstances: 1,11 browserName: 'chrome',12 acceptInsecureCerts: true,13 'goog:chromeOptions': {14 binary: chromiumPath,15 args: ['--disable-infobars', '--window-size=1920,1080'],16 },17 },18 ],19}
You need to set up automationProtocol: 'devtools'
option in your config instead of default webdriver
protocol for now. This may change in future updates.
Run your tests
With configration set up, you can run your tests the same way as before. After your run finishes, your recordings will be stored locally.
Upload your replays
Upload your replays with the following command:
Terminal
replayio upload --all
To learn more see the docs on Replay CLI.
After you upload your recordings, you can view them in Test Suite Dashboard.
You can try this out on your own, by forking this example repository.
Learn how to manage your recordings, debug your app using Replay DevTools and more
Manage your recordings
Learn how to upload, remove and view your recordings using CLI
Replay DevTools
Learn how to use Replay DevTools to debug your tests.
Setting up a team
Learn how to create a team in the Replay App
Test Suite Management
Test Suite Dashboard helps you stay on top of your test suite health.