A spreadsheet with 500 rows may contain 500 test cases. It may also turn a single sign-in check into three useless cases: “Enter username”, “Enter password” and “Click Sign in”. Before importing anything, decide where each independently verifiable expectation ends.
Classify a handful of rows first
Work on a copy. Pick five to ten representative rows, including one clear case, a multi-step sequence and a note left over from the last run. Write down what each one should become in the project.
| Source entry | What to do with it |
|---|---|
| “Sign in as a customer; home page appears” | One case. Add the role and starting state as prerequisites. Specify what the customer should see after signing in. |
| “Create request” on row 8; “Reload list” on row 9 | If these are two steps in one check, give them the same grouping value. After reload the request should still be there. |
| Two departments both have a case called “Create request” | Matching titles do not prove duplication. Compare the roles, data and expected outcomes before merging. |
| “23 May: OK, tested by AB” | A historical result. Preserve it in the source records. Keep the reusable procedure independent of that run. |
| “As above” in a merged cell | Repeat the intended group value in each relevant row. Sorting the sheet should not change what a row means. |
A pilot small enough to count by hand
Before a trial import, predict its outcome. For example, enter these four steps in a copy of the workbook to prepare two quick test cases:
| Group | Step |
|---|---|
| Save request | Submit a new request |
| Save request | Reload the list and compare the reference |
| Check required field | Submit an empty form |
| Check required field | Fill in the missing field and submit again |
Expect two cases, each with two quick rows. In the Windows client, select a test unit and open the Excel import from its Import/Export menu. Check the sheet, header row and preview. Map “Group” to the test case title and choose it as the source grouping field for quick rows. Then map “Step” to the corresponding quick-row field. The Excel import guide shows the mappings and the resulting cases.
Know what to fix before importing the rest
Open both cases in a separate test project. Are the steps in the right order? Could a colleague who has never seen the spreadsheet perform the check and recognise success? Four cases instead of two suggest a grouping problem. Two cases with vague instructions point to a problem in the source text. Fix the relevant cause and repeat the small trial before migrating the whole library.