Test Data Requirement Analysis

Analyze entity, field, relationship, state, role, privacy, source, lifecycle, setup, and cleanup requirements before test design or data generation. Produce TDR-## requirements and blockers. Do not generate data, read production data, or copy the test-data-generation dataset plan.

When to Use

• Use it to determine which entities, fields, states, roles, and relationships a scenario needs.
• Use it to find schema, source, masking, isolation, lifecycle, cleanup, and environment prerequisite gaps.
• Use it when data material is incomplete but a constrained requirement list can be consumed by test design or data generation.

Do not use it to create records, call real data sources, copy production data, write full cases, or execute tests.

Output Format Options

• Use Markdown by default; when a table, CSV, or JSON is requested, preserve the same evidence, status, impact, owner, and validation fields.
• Do not present a structured format or static inventory as execution, pass, approval, or release evidence.

How to Use