Quickstart
The fastest way to generate and deploy E2E UI tests!
Last updated
Was this helpful?
The fastest way to generate and deploy E2E UI tests!
Last updated
Was this helpful?
TestDriver's AI QA Agents make it easy and fast to generate and deploy powerful tests. Here's how you can get started quickly with TestDriver.
The quickest way to create your first tests is with the Test Generation demo. TestDriver will log into your app, generate a dozen tests, and upload them to GitHub.
The testdriverai
node package makes it super easy to generate tests using natural language instructions.
Install the testdriverai
package with npm
or yarn
.
Then, run testdriverai init in the directory you want to make your new test project.
TestDriver will launch interactive setup:
The TestDriver Running Tests are the fastest and easiest way to get started with TestDriver, but you'll need an API key. You can get one by subscribing to TestDriver Pro in the TestDriver dashboard. See Getting an API Key.
Every TestDriver Pro plan comes with $100 of free credits
Paste the API key from your dashboard into the interactive setup. Complete the rest of the questions.
You can always use your own computer as a runner for free. See Local Agent Setup.
Now it's time for the fun part, building tests. Run testdriverai [file]to trigger the agent.
Tell TestDriver what you want it to do. See Prompting.
It's time to test! The following command will launch TestDriver in interactive mode. TestDriver will generate test commands and save them totestdriver/test.yml
.
Now, just tell TestDriver what you want it to do. For our example, try click new task
.
TestDriver will look at your screen and generate a test script. TestDriver can see the screen, control the mouse, keyboard, and more!
TestDriver will execute the command
s found in the yml
codeblocks of the response.
See the yml
TestDriver generated? That's our own schema. You can learn more about it in the Test Steps.
Take your hands off the mouse and keyboard while TestDriver executes! TestDriver is not a fan of backseat drivers.
Feel free to ask TestDriver to perform some more tasks. Every time you prompt TestDriver it will look at your screen and generate more test step to complete your goal.
If something didn't work, you can use /undo
to remove all of the test steps added since the last prompt.
Now it's time to make sure the test plan works before we deploy it. Use testdriver run
to run the test file you just created with /save
.
Check out Running Testsand GitHub Actionto deploy tests within CI/CD.