Test a CSV import and the column mapping behind it

Failure modes in this flow

The source column names deliberately do not match the target fields, which is what makes the mapping worth asserting rather than assuming.

Asserting the mapping table and then the resulting record is the pairing that matters. The mapping screen is a promise and the record is whether it was kept, and an import can display one mapping while applying another.

Writing the objective

The row count is asserted before the import runs, so a file that is partially read fails before any records are created.

---
mode: testing
url: https://my-testing-repo-main.vercel.app/zoho-clone-app/import?reset=true
max_steps: 45
tags: [zoho-crm, crm, import]
---

# Zohoe CRM 32.1: Lead import mapping

Catalog objective: import a small CSV of leads with field mapping.
Key assertion: the leads are created with the mapped fields.

## Read the file
Click "Read the file" and verify a "Map the columns" card appears with "Rows found" of 3.

## Verify the mapping
Verify the mapping table maps "Given Name" to "First Name", "Surname" to "Last Name", "Organisation" to "Company", "Work Email" to "Email", "Channel" to "Lead Source" and "Value" to "Deal Amount".

## Run the import
Click "Import 3 leads" and verify a green banner titled "Import complete" reads "3 leads created."

## Verify the mapped values landed on the record
Verify the "First imported record" card shows "Lead id" of "L2", "First Name" of "Sam", "Last Name" of "Rivera", "Company" of "Riverfield FC", "Email" of "sam@riverfield.test", "Lead Source" of "Web" and "Deal Amount" of "52000".

The created record is asserted field by field rather than by a count, because an import that creates the right number of records with shifted values is the failure this test exists to catch.

The assertions in detail

A read, a mapping, the import and the record.

Checking one record in full is more useful than checking all three shallowly. A shifted mapping shows up on any row, and the detail is what makes it diagnosable.

Running it locally

kane-cli testmd run tests/zoho-crm/lead-import-mapping_test.md

Add a file with a malformed row, since an import that silently skips it is worse than one that refuses the file.

Migrations happen once and are hard to unwind. File handling in Kane CLI covers the upload side, and evidence based QA covers keeping proof of what was imported.