Test Data Management

Learning objectives#

• Create unique data per test
• Use builders and factories
• Seed data through APIs instead of the UI
• Clean up and isolate environments

Explanation#

Each test should create its own data (unique emails, product names) so tests can run in parallel and in any order.

Builders/factories produce valid objects with sensible defaults; tests override only what matters.

Seed data through APIs or SQL — faster and more reliable than clicking through the UI.

Never depend on production data. Keep credentials and URLs in environment config.

Code example: A data factory for tests#

1import { randomUUID } from 'node:crypto';
2import type { APIRequestContext } from '@playwright/test';
3

4export function aCustomer(overrides: Partial<{ name: string; email: string }> = {}) {
5  const id = randomUUID().slice(0, 8);
6  return { name: `Test User ${id}`, email: `qa+${id}@example.com`, password: 'Passw0rd!', ...overrides };
7}
8

9export async function createCustomer(request: APIRequestContext, overrides = {}) {
10  const customer = aCustomer(overrides);
11  const res = await request.post('/api/test-support/customers', { data: customer });
12  if (!res.ok()) throw new Error(`Seeding failed: ${res.status()}`);
13  return { ...customer, id: (await res.json()).id as number };
14}
15

16// In a test:
17// const asha = await createCustomer(request, { name: 'Asha' });
18// ...test...  then  await request.delete(`/api/test-support/customers/${asha.id}`);

Every test gets its own customer with a unique email, created in milliseconds through the API.

This example is illustrative. Copy or download it and run it in your own environment; the expected output is shown above.

Step-by-step explanation#

1. randomUUID makes names and emails unique.
2. Defaults keep tests short; overrides express intent.
3. A test-only API seeds data quickly.
4. Tests delete what they created.

Real-world use case#

Common mistakes#

Best practices#

• Unique data per test
• Builders with defaults
• Seed via API/SQL
• Protect test-support endpoints from production

Remember this#

Practice exercise#

1They bypass normal rules (e.g. create users directly) and would be a security hole.

Mini quiz#

Want more? Practise all Automation Testing MCQs · Automation Testing interview questions

Related topics#

My notes#

Saved in this browser.