QA interview guide

How would you test CSV import?

CSV and Excel import flows are data quality traps. A strong answer covers file validation, schema mapping, row-level errors, duplicate handling, rollback, permissions, and whether users can recover from bad imports.

Practice this scenarioBrowse all questions

Write your own answer and compare it with senior QA coverage.

What interviewers expect

What interviewers expect

Interviewers expect valid file formats, missing columns, extra columns, row errors, duplicates, preview, mapping, partial success, rollback, error reports, database consistency, security, and performance with large files.

Checklist

Checklist

Use these practical prompts to build a complete answer. Strong interview responses usually include functional behavior, negative cases, security, backend/data risks, UX, accessibility, and reliability.

Functional import behavior

  • Valid CSV and valid Excel files import expected records with correct field mapping.
  • Header row, required columns, optional columns, extra columns, column order, and case differences are handled.
  • Preview, mapping, confirm import, cancel import, and import summary work.
  • Created, updated, skipped, failed, and duplicate row counts are accurate.
  • Imported records can be searched, viewed, edited, or exported after import.

Validation and error handling

  • Invalid file type, empty file, wrong delimiter, bad encoding, huge file, and password-protected file are rejected.
  • Missing required columns, invalid dates, invalid numbers, invalid email, long values, and Unicode values are reported.
  • Duplicate rows within the file and duplicates against existing records follow business rules.
  • Partial import, all-or-nothing rollback, retry, and re-upload behavior are verified.
  • Error report identifies row number, column, reason, and recovery action.

Security, backend, and data consistency

  • CSV formula injection, XSS, malicious file content, and unsafe filenames are handled.
  • Unauthorized users cannot import or overwrite restricted records.
  • Tenant isolation, permissions, ownership, protected fields, and audit logs are enforced.
  • Database transaction, rollback, idempotency, queue processing, and worker restart are tested.
  • Emails, events, notifications, or downstream sync triggered by import are correct and not duplicated.

UX, accessibility, and performance

  • Progress state, long-running import status, cancel behavior, and completion messages are clear.
  • Keyboard navigation, labels, focus states, and screen reader status announcements work.
  • Large files, many rows, many validation errors, and slow processing stay within expected performance.
  • Browser memory, timeout, network failure, and backend 500 states are recoverable.
  • Metrics, logs, alerts, and support diagnostics help investigate failed imports.

Complete interview coverage checklist

Aim to mention 20-40 concrete checks. This expanded list helps you turn a short answer into a structured senior-style response.

Valid CSV and valid Excel files import expected records with correct field mapping.
Header row, required columns, optional columns, extra columns, column order, and case differences are handled.
Preview, mapping, confirm import, cancel import, and import summary work.
Created, updated, skipped, failed, and duplicate row counts are accurate.
Imported records can be searched, viewed, edited, or exported after import.
Invalid file type, empty file, wrong delimiter, bad encoding, huge file, and password-protected file are rejected.
Missing required columns, invalid dates, invalid numbers, invalid email, long values, and Unicode values are reported.
Duplicate rows within the file and duplicates against existing records follow business rules.
Partial import, all-or-nothing rollback, retry, and re-upload behavior are verified.
Error report identifies row number, column, reason, and recovery action.
CSV formula injection, XSS, malicious file content, and unsafe filenames are handled.
Unauthorized users cannot import or overwrite restricted records.
Tenant isolation, permissions, ownership, protected fields, and audit logs are enforced.
Database transaction, rollback, idempotency, queue processing, and worker restart are tested.
Emails, events, notifications, or downstream sync triggered by import are correct and not duplicated.
Progress state, long-running import status, cancel behavior, and completion messages are clear.
Keyboard navigation, labels, focus states, and screen reader status announcements work.
Large files, many rows, many validation errors, and slow processing stay within expected performance.
Browser memory, timeout, network failure, and backend 500 states are recoverable.
Metrics, logs, alerts, and support diagnostics help investigate failed imports.
Structure your answer: Start with valid CSV/Excel import, mapping, preview, confirmation, and imported data verification.
Structure your answer: Add validation: file type, columns, delimiters, encoding, row formats, duplicates, and error reports.
Structure your answer: Add data and security: permissions, protected fields, formula injection, transactions, rollback, and audit logs.
Structure your answer: Close with progress UX, accessibility, large files, queue failures, retries, and observability.
Do not miss: Row-level error report quality.
Do not miss: All-or-nothing rollback versus partial import rules.
Do not miss: CSV formula injection and protected-field updates.
Do not miss: Queue or worker failure during long-running import.

Ready to practice?

Practice this scenario interactively

Write your own answer and compare it with senior QA coverage.

Practice this scenario

Answer structure

Strong answer structure

  1. Start with valid CSV/Excel import, mapping, preview, confirmation, and imported data verification.
  2. Add validation: file type, columns, delimiters, encoding, row formats, duplicates, and error reports.
  3. Add data and security: permissions, protected fields, formula injection, transactions, rollback, and audit logs.
  4. Close with progress UX, accessibility, large files, queue failures, retries, and observability.

Common missed areas

Common missed risks

Row-level error report quality.
All-or-nothing rollback versus partial import rules.
CSV formula injection and protected-field updates.
Queue or worker failure during long-running import.

Answer template

Use this interview answer template

I would start with valid CSV and Excel import, then cover file format, headers, column mapping, row validation, duplicate rows, partial import, rollback, error reports, permissions, formula injection, queue failures, UX, accessibility, and performance for large files.

Use it as a structure, then replace the examples with specific checks for the feature you are discussing.

Common weak answer

“I would test valid and invalid cases.”

This is too generic because it does not show risk thinking. A stronger answer names the happy path, negative cases, security risks, backend/data behavior, UX/accessibility, and reliability concerns that matter for this exact scenario.

Examples

Weak answer vs stronger answer

Weak answer
“I would upload a valid CSV and invalid file.”

This covers basic file acceptance, but misses row-level validation, mapping, duplicates, rollback, error reports, permissions, security, performance, and backend processing.

Stronger answer
“I would test valid CSV and Excel import, required and optional columns, extra columns, column order, preview mapping, confirm and cancel import, missing columns, invalid dates, invalid numbers, invalid email, long values, Unicode, wrong delimiter, bad encoding, empty file, huge file, duplicate rows, existing duplicates, partial import, rollback, retry, error report with row and column reasons, imported records visible afterward, unauthorized import blocked, tenant isolation, protected fields, formula injection, audit logs, queue processing, worker restart, progress state, screen reader status, large file performance, logs, metrics, and alerts.”

FAQ

Frequently asked questions

What should I mention first when answering "How would you test CSV import?"

Start with valid CSV/Excel import, mapping, preview, confirmation, and imported data verification.

Should I include negative and edge cases?

Invalid file type, empty file, wrong delimiter, bad encoding, huge file, and password-protected file are rejected. Missing required columns, invalid dates, invalid numbers, invalid email, long values, and Unicode values are reported.

Should I include security, API, or backend risks?

CSV formula injection, XSS, malicious file content, and unsafe filenames are handled. Unauthorized users cannot import or overwrite restricted records.

What are common missed risks?

Row-level error report quality. All-or-nothing rollback versus partial import rules. CSV formula injection and protected-field updates. Queue or worker failure during long-running import.

How can I practice this answer?

Use the interactive how would you test csv import? challenge to write your own answer, get checklist-based feedback, and compare your coverage with stronger QA thinking.

Practice

Practice this scenario interactively

Write your own answer and compare it with senior QA coverage.

Practice this scenario