Skip to content
cccskills
FreePublished on GitHub

testdriver:locating-elements

Find UI elements using natural language descriptions

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md1.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

<!-- Generated from locating-elements.mdx. DO NOT EDIT. -->

Locating Single Elements

Use natural language to describe elements. Descriptions should be specific enough to locate the element, but not too-specific that they break with minor UI changes. For example:

await testdriver.find('email input field');
await testdriver.find('first product card in the grid');
await testdriver.find('dropdown menu labeled "Country"');

<Info>TestDriver will cache found elements for improved performance on subsequent calls. Learn more about element caching here.</Info>

Debugging Found Elements

After finding an element, you can inspect its properties for debugging:

const button = await testdriver.find('submit button');
console.log(button);

This outputs all element properties:

{
  description: 'submit button',
  found: true,
  x: 150,
  y: 300,
  coordinates: { x: 150, y: 300, centerX: 200, centerY: 320 },
  threshold: 0.8,
  confidence: 0.95,
  similarity: 0.92,
  selector: 'button[type="submit"]',
  cache: {
    hit: true,
    strategy: 'pixel-diff',
    createdAt: '2025-01-15T10:30:00Z',
    diffPercent: 0.02,
    imageUrl: 'https://...'
  }
}

Working with Multiple Elements

Find and interact with multiple elements:

// Find all matching elements
const products = await testdriver.findAll('product card');
console.log(`Found ${products.length} products`);

// Interact with each
for (const product of products) {
  const title = await product.find('title text');
  console.log('Product:', title.text);

  await product.find('add to cart button').click();
}

// Or find specific element
const firstProduct = products[0];
await firstProduct.click();

Reviews

No reviews yet. Tell others what you thought.

Comments

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.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

How the TestDriver agent behaves on GitHub issues, pull requests, and @mentions

The English summary is being prepared. Showing the original description.

testdriverai/testdriverai406Updated Sep 21, 2026

Execute natural language tasks using AI

The English summary is being prepared. Showing the original description.

testdriverai/testdriverai406Updated Sep 21, 2026

Make AI-powered assertions about screen state

The English summary is being prepared. Showing the original description.

testdriverai/testdriverai406Updated Sep 21, 2026

Deploy TestDriver on your AWS infrastructure using CloudFormation

The English summary is being prepared. Showing the original description.

testdriverai/testdriverai406Updated Sep 21, 2026

Speed up tests with screenshot-based caching

The English summary is being prepared. Showing the original description.

testdriverai/testdriverai406Updated Sep 21, 2026

How TestDriver learns your app and caches what it discovers for instant, deterministic replays

The English summary is being prepared. Showing the original description.

testdriverai/testdriverai406Updated Sep 21, 2026

See all skills by testdriverai

Report a problem with this skill