testdriver:agent
FreeHow the TestDriver agent behaves on GitHub issues, pull requests, and @mentions
The English summary is being prepared. Showing the original description.
Handle async operations and prevent flaky tests
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
By default, find() automatically polls for up to 10 seconds, retrying every 5 seconds until the element is found. This means most elements that appear after short async operations will be found without any extra configuration.
For longer operations, increase the timeout:
// Default behavior - polls for up to 10 seconds automatically
const element = await testdriver.find('Loading complete indicator');
await element.click();
// Wait up to 30 seconds for slower operations
const element = await testdriver.find('Loading complete indicator', { timeout: 30000 });
await element.click();
// Useful after actions that trigger loading states
await testdriver.find('submit button').click();
await testdriver.find('success message', { timeout: 15000 });
// Disable polling for instant checks
const toast = await testdriver.find('notification toast', { timeout: 0 });
TestDriver automatically waits for the screen and network to stabilize after each action using redraw detection. This prevents flaky tests caused by animations, loading states, or dynamic content updates.
<Note> Redraw detection adds a small delay after each action but significantly reduces test flakiness. </Note>For example, when clicking a submit button that navigates to a new page:
// Click submit - TestDriver automatically waits for the new page to load
await testdriver.find('submit button').click();
// By the time this runs, the page has fully loaded and stabilized
await testdriver.assert('dashboard is displayed');
await testdriver.find('welcome message');
Without redraw detection, you'd need manual waits or retries to handle the page transition. TestDriver handles this automatically by detecting when the screen stops changing and network requests complete.
You can disable redraw detection or customize its behavior:
// Disable redraw detection for faster tests (less reliable)
const testdriver = TestDriver(context, {
redraw: false
});
Here is an example of customizing redraw detection:
// Fine-tune redraw detection
const testdriver = TestDriver(context, {
redraw: {
enabled: true,
diffThreshold: 0.1, // Pixel difference threshold (0-1)
screenRedraw: true, // Monitor screen changes
networkMonitor: true, // Wait for network idle
}
});
wait()For simple pauses — waiting for animations, transitions, or state changes after an action — use wait():
// Wait for an animation to complete
await testdriver.find('menu toggle').click();
await testdriver.wait(2000);
// Wait for a page transition to settle
await testdriver.find('next page button').click();
await testdriver.wait(1000);
<Note>
For waiting for specific **elements** to appear, prefer `find()` with a `timeout` option. Use `wait()` only for simple time-based pauses.
</Note>No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
How the TestDriver agent behaves on GitHub issues, pull requests, and @mentions
The English summary is being prepared. Showing the original description.
Execute natural language tasks using AI
The English summary is being prepared. Showing the original description.
Make AI-powered assertions about screen state
The English summary is being prepared. Showing the original description.
Deploy TestDriver on your AWS infrastructure using CloudFormation
The English summary is being prepared. Showing the original description.
Speed up tests with screenshot-based caching
The English summary is being prepared. Showing the original description.
How TestDriver learns your app and caches what it discovers for instant, deterministic replays
The English summary is being prepared. Showing the original description.