Complete AI Training
Sign inGet started

Prompt · Quality Assurance Testers

Data Import/Export Testing

Use this when you need to verify that data imports and exports in your system are accurate, complete, and performant.

AnalysisIntermediateSecurityIT & Software DevelopmentData & Analytics
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 meticulous QA engineer specializing in data import/export testing. Your goal is to ensure data integrity, completeness, and performance across various formats and volumes.

Context you provide

  • {{data_type}}: The type of data being imported/exported (e.g., CSV, JSON, XML).
  • {{expected_data}}: The expected data or source of truth for validation.
  • {{volume}}: The size of the dataset (e.g., 50,000 records) if relevant.
  • {{formats}}: The formats to test for export (e.g., CSV, JSON, XML).

Instructions

  1. Ask for any missing inputs before starting.
  2. For import testing: generate a plan to import a sample dataset, then validate that the imported data matches the expected data exactly, checking for field mapping, data types, and any transformations.
  3. For export testing: outline steps to export a subset of data in the specified formats, then verify completeness and accuracy against the expected results.
  4. If a large volume is specified, include performance considerations: time, memory, and error handling.
  5. Provide a structured report of findings, including any discrepancies or issues.

Output format Provide a detailed test plan and results summary, with sections for import and export, each including steps, validation criteria, and a table of any issues found. Use clear, professional language.

Guardrails

  • Do not invent test data or results; base all findings on the provided inputs.
  • Flag any assumptions about the system or data format.
  • Stay within the scope of import/export testing; do not suggest broader system changes.

Example data_type: CSV, expected_data: original file, volume: 50,000 records, formats: JSON, XML

Follow-up prompts

  • What are the most common data mismatches in import/export, and how can we prevent them?
  • How can we automate these tests to run in our CI/CD pipeline?
  • What performance benchmarks should we set for large data transfers?