testdino-hq/playwright-skill / frontend
playwright-frontend
VerifiedFor frontend engineers authoring UI — how to make components reliably locatable by tests and AI agents. Covers the official Playwright locator priority, semantic/accessible markup first, and how to add valid, unique, stable `data-testid` attributes (naming convention, uniqueness in lists, stability rules) for React, Vue, Angular, and Svelte. Use when writing or reviewing components, or when an agent needs durable locators.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.5 KB |
| data-testid-conventions.md | markdown | 13.9 KB |
| examples.md | markdown | 6.6 KB |
examples.md
View on GitHub# Framework Patterns for `data-testid`
Copy-paste patterns for placing valid, unique, stable `data-testid` attributes. Follow the naming and stability rules in [data-testid-conventions.md](data-testid-conventions.md).
---
## React / JSX
```jsx
// Semantic markup FIRST (getByRole works), test IDs for durable handles.
function LoginForm({ onSubmit }) {
return (
<form data-testid="login-form" onSubmit={onSubmit}>
<label htmlFor="email">Email</label>
<input id="email" type="email" data-testid="login-form-email-input" />
<p role="alert" data-testid="login-form-email-error" />
<label htmlFor="password">Password</label>
<input id="password" type="password" data-testid="login-form-password-input" />
<button type="submit" data-testid="login-form-submit-button">
Sign in
</button>
</form>
);
}
```
Lists — stable entity key, never the index:
```jsx
function UserTable({ users }) {
return (
<table data-testid="users-table">
<tbody>
{users.map((user) => (
<tr key={user.id} data-testid={`user-row-${user.id}`}>
<td data-testid={`user-row-${user.id}-name`}>{user.name}</td>
<td>
<button data-testid={`user-row-${user.id}-delete-button`}>
Delete
</button>
</td>
</tr>
))}
</tbody>
</table>
);
}
```
Toggle swatch — a native `<button>` gives role, focus and Enter/Space for free; the test ID tells identical swatches apart by a stable key:
```jsx
function ColorSwatch({ color, selected, onSelect }) {
return (
<button
type="button"
aria-pressed={selected}
aria-label={`Select ${color}`}
data-testid={`color-swatch-${color}`}
onClick={onSelect}
/>
);
}
```
---
## Vue 3 (SFC)
```vue
<template>
<form data-testid="login-form" @submit.prevent="onSubmit">
<label for="email">Email</label>
<input id="email" v-model="email" data-testid="login-form-email-input" />
<button type="submit" data-testid="login-form-submit-button">Sign in</button>
</form>
<ul data-testid="users-list">
<li
v-for="user in users"
:key="user.id"
:data-testid="`user-row-${user.id}`"
>
{{ user.name }}
<button :data-testid="`user-row-${user.id}-delete-button`">Delete</button>
</li>
</ul>
</template>
```
> Note: static IDs use `data-testid="..."`, dynamic ones use the bound form `:data-testid="..."`.
---
## Angular (17+ control flow)
```html
<form data-testid="login-form" (ngSubmit)="onSubmit()">
<label for="email">Email</label>
<input id="email" [(ngModel)]="email" data-testid="login-form-email-input" />
<button type="submit" data-testid="login-form-submit-button">Sign in</button>
</form>
<ul data-testid="users-list">
@for (user of users; track user.id) {
<li [attr.data-testid]="'user-row-' + user.id">
{{ user.name }}
<button [attr.data-testid]="'user-row-' + user.id + '-delete-button'">
Delete
</button>
</li>
}
</ul>
```
> Use `[attr.data-testid]="..."` for dynamic values (Angular needs `attr.` to bind to a real DOM attribute). Static values can stay as plain `data-testid="..."`. Key `@for` with `track` on the same entity id (on Angular 16 and older, `*ngFor` with a `trackBy` on that id).
---
## Svelte 5
```svelte
<script>
let { users, onSubmit } = $props();
let email = $state('');
function handleSubmit(event) {
event.preventDefault();
onSubmit({ email });
}
</script>
<form data-testid="login-form" onsubmit={handleSubmit}>
<label for="email">Email</label>
<input id="email" bind:value={email} data-testid="login-form-email-input" />
<button type="submit" data-testid="login-form-submit-button">Sign in</button>
</form>
<ul data-testid="users-list">
{#each users as user (user.id)}
<li data-testid={`user-row-${user.id}`}>
{user.name}
<button data-testid={`user-row-${user.id}-delete-button`}>Delete</button>
</li>
{/each}
</ul>
```
---
## Centralizing test IDs
Share one source of truth between the app and the test suite so renames are a single edit and typos are caught by the compiler.
```ts
// testIds.ts (imported by both components and tests)
export const testIds = {
loginForm: {
root: 'login-form',
email: 'login-form-email-input',
password: 'login-form-password-input',
submit: 'login-form-submit-button',
},
userRow: (id: string | number) => `user-row-${id}`,
userRowDelete: (id: string | number) => `user-row-${id}-delete-button`,
} as const;
```
```jsx
import { testIds } from './testIds';
<button data-testid={testIds.loginForm.submit}>Sign in</button>
{users.map((u) => (
<tr data-testid={testIds.userRow(u.id)} key={u.id}>
<button data-testid={testIds.userRowDelete(u.id)}>Delete</button>
</tr>
))}
```
```ts
// In the test — same constants, no magic strings.
import { testIds } from '../src/testIds';
await page.getByTestId(testIds.loginForm.submit).click();
await page.getByTestId(testIds.userRowDelete(42)).click();
```
---
## Production stripping (optional)
Only if your team decides test IDs shouldn't ship to real production. **Keep them in dev, CI, and staging** — those are the environments tests and agents run against.
React (Babel) — `.babelrc` for production builds only:
```json
{
"env": {
"production": {
"plugins": [
["react-remove-properties", { "properties": ["data-testid"] }]
]
}
}
}
```
Next.js — `next.config.js`:
```js
module.exports = {
compiler: {
// Strips in production builds; leaves dev/test untouched.
reactRemoveProperties: process.env.NODE_ENV === 'production',
},
};
```
Vue/Vite — a template compiler node transform, enabled only in production mode:
```js
// vite.config.js
import { defineConfig } from 'vite';
import vue from '@vitejs/plugin-vue';
const ELEMENT = 1, ATTRIBUTE = 6, DIRECTIVE = 7; // @vue/compiler-core NodeTypes
function stripTestIds(node) {
if (node.type !== ELEMENT) return;
node.props = node.props.filter((p) =>
!(p.type === ATTRIBUTE && p.name === 'data-testid') &&
!(p.type === DIRECTIVE && p.name === 'bind' && p.arg?.content === 'data-testid'));
}
export default defineConfig(({ mode }) => ({
plugins: [
vue({ template: { compilerOptions: { nodeTransforms: mode === 'production' ? [stripTestIds] : [] } } }),
],
}));
```
Verify your staging/CI build does **not** strip, or your suite will lose every locator.
> Decision guide: stripping reduces payload and hides internals, but adds build complexity and a foot-gun (stripping the wrong env breaks all tests). Many teams simply ship `data-testid` — it's a few bytes and harmless. Strip only when there's a concrete reason.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |