Testdriver

What is Testdriver?

Testdriver is an AI assistant for software engineers that helps you build tests that are easy to maintain. You write tests in plain, natural language from your command line — no selectors required. Testdriver interacts with your application like a human QA tester, then generates YML test files with optimized instructions for repeating those tests.

It includes fuzzy matching and self-healing capabilities, so tests adapt when your application changes. You can also run tests automatically on secure, temporary virtual machines using GitHub Actions.

The tool is built specifically for engineers and integrates with GitHub. It aims to eliminate complex automated test scripts and reduce manual testing, freeing you to focus on coding. It supports end-to-end exploratory testing and lets developers see exactly what’s happening during test runs.

Two limitations to note: it currently only integrates with GitHub and relies on Dashcam.io.

Who created Testdriver?

Testdriver was created by Dashcam.io. The company focuses on bringing AI-driven capabilities to testing workflows.

What is Testdriver used for?

• Build durable tests that stay functional even when your application changes.
• Write tests in natural language through the CLI — just tell Testdriver what to do.
• Generate YML test files with clear, optimized instructions for repeating tests.
• Deploy tests automatically using GitHub Actions.
• Run end-to-end and exploratory testing to uncover unexpected issues.
• View screen logs while testing is in progress.

Who is Testdriver for?

Testdriver is designed for engineers who want to reduce manual testing and avoid writing complex automated test scripts.

How to use Testdriver?

1. Run $ testdriver in your CLI to get started.
2. Instruct Testdriver in natural language — for example, “Fill out the form with fake information.”
3. Alternatively, provide instructions in a YAML file, which Testdriver uses to automatically generate and run your tests.
4. Use the GitHub integration to deploy tests via GitHub Actions.
5. During a test run, view Testdriver’s screen, logs, and AI actions to understand how it makes decisions.