Create a focused exploratory-testing charter for a CSV import.

Instruction: Write the charter, a time allocation, and the evidence you would return after the session.

Context:

A fictional staging application imports up to 500 inventory rows from CSV. The release changed column mapping and added Cancel during validation. Imports must either apply all valid rows together or apply none; a file containing any invalid row must be rejected without changes. Cancelling before Apply must leave inventory unchanged. You have 30 minutes, a resettable synthetic inventory fixture, and sample CSV files with duplicates, missing required fields, and reordered columns. Loading, error messages, and recovery behavior have not been explored. No production data or load testing is permitted.

Updated

Official answer available

Read the opening below, then unlock the full answer and practical guidance.

My charter would be: explore column mapping, cancellation, and correction of failed imports using the supplied synthetic files to find ways inventory can change without a successful Apply or ways users lose the information needed to recover. That gives the session a mission without prescribing every click...

Upgrade to view official answer

Related Questions