Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →testdriverai/testdriver:ci-cd
Run TestDriver tests in CI/CD with parallel execution and cross-platform support
Passed 21 of 22 test cases with the skill, and 4 of 22 without it.
and 25 more in the full report
17 fixed4 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 17 test cases the skill fixed. Same model, same prompt, with and without the skill.
In a Vitest cross-platform test script, once TestDriver is initialized with the target platform, what specific API method call is used to provision a Chrome browser navigating to 'https://example.com', and what method performs natural language verification on the resulting page?
| Checked | Without skill | With skill |
|---|---|---|
| Provisions Chrome using testdriver.provision.chrome with a url property | Missed | Passed |
| Executes assertions using testdriver.assert with an English description string | Passed | Passed |
The instructions your model reads when the skill loads.
TestDriver integrates with the common CI providers. It lets you do automated end-to-end tests on each push and pull request.
On GitHub Actions, use OIDC through the published testdriverai/action. Then
there is no TD_API_KEY secret to store, copy, or change. The action shows that the
workflow runs in your org. TestDriver changes that proof for your
team's key at run time. See the GitHub Actions tab below.
For other CI providers (or self-hosted runners without OIDC), use a
stored API key from console.testdriver.ai/settings.
Add it as a TD_API_KEY secret in the settings of your CI provider.
Use the published [`testdriverai/action`](https://github.com/testdriverai/action). It makes the OIDC token, changes it for your team's API key, and exports `TD_API_KEY` for the steps that come after. **There is no `TD_API_KEY` secret to store or change.**
<Note>
Do this one time: authorize the [TestDriver GitHub App](https://console.testdriver.ai) for your org. Then the org → team binding exists. If your org authorized the App before OIDC support was available, authorize it again one time. If the App is not authorized, the action fails with a console link. (Or it uses the `api-key` secret if you give one.)
</Note>
```yaml .github/workflows/testdriver.yml
name: TestDriver Tests
on:
push:
branches: [main]
pull_request:
branches: [main]
test cases passed, vs 4 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.