Check whether the outcome improved
Verify the uninterrupted control
Run a controlled import with a known file, mapping, and options. Record the approved input set and compare exact final values. This establishes a readable baseline before adding replacement or navigation cases, and prevents a separate ordinary parsing issue from being misclassified as preview drift.
Exercise input changes around review
Replace a same-named file, revise a mapping, and revisit preview through supported navigation. Check whether the displayed review reflects the new input or clearly requires confirmation again. Use distinct fixture values so it is possible to tell which source and column assignments execution actually consumed.
Check delayed and competing edits
Where execution is queued or settings can be edited concurrently, change the relevant configuration after confirmation in a controlled case. Verify the documented behavior: execution uses the approved revision or stops for a clear new review. Inspect saved values rather than relying only on an unchanged preview screenshot.
What to carry forward
Accept when every exercised path preserves the approved inputs or explicitly obtains a new review before executing different work. Record delayed and concurrent cases that were not available to test. Keep verification open when the exact executed source or mapping revision cannot be read back or inferred from distinct fixture values.
Technical background: Django import-export documentation.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow