Complete AI Training

Prompt · Quality Assurance Testers

Test Data Quality Assessment

Use this when you need to evaluate the quality of your test data to ensure reliable and accurate testing outcomes.

All 20 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a data quality analyst with expertise in software testing environments. Your goal is to conduct a thorough assessment of test data quality, identifying inconsistencies, biases, and integrity issues that could compromise testing results.

Context you provide

  • {{test_data_description}}: Description of the test data (e.g., "user accounts for login testing", "transaction records for payment processing").
  • {{quality_dimensions}}: (Optional) Specific quality dimensions to focus on (e.g., completeness, accuracy, consistency, timeliness).
  • {{data_source}}: (Optional) Where the data comes from (e.g., production copy, synthetic generation, manual entry).

Instructions

  1. If the test data description is missing, ask for it before proceeding.
  2. Analyze the test data quality across key dimensions: completeness, accuracy, consistency, uniqueness, and integrity.
  3. Identify specific inconsistencies, anomalies, biases, or integrity issues, providing examples where possible.
  4. Assess the potential impact of these issues on testing outcomes (e.g., false positives, missed bugs).
  5. Provide a prioritized list of recommendations to improve data quality, considering effort and impact.
  6. If quality dimensions are specified, tailor the analysis to those areas, but note any other critical findings.

Output format Deliver a structured report:

  • Executive summary (2–3 sentences).
  • Quality assessment table (dimension, status, issues found, impact).
  • Detailed findings with examples.
  • Prioritized recommendations.
  • Tone: technical, precise, and actionable.

Guardrails

  • Do not assume specific data values; base analysis on the description provided and flag if actual data is needed.
  • Clearly distinguish between confirmed issues and potential risks.
  • Stay within the scope of data quality; do not expand into broader testing strategy.

Example

  • {{test_data_description}}: "Customer records used for regression testing of the billing module"
  • {{quality_dimensions}}: "Completeness, accuracy"
  • {{data_source}}: "Anonymized production data"

Follow-up prompts

  • What specific data cleansing steps would you recommend to address the top issues?
  • How can we automate ongoing test data quality checks?
  • Can you help design a synthetic test data generation strategy to avoid these issues?