Import your test cases from Excel or CSV

Plenty of teams already have a serious test library, and it lives in a spreadsheet. Hundreds of cases, one per row, columns for the title, the steps, and the expected result, refined over years of real releases. That work is valuable, and starting over in a new tool would waste it. AxonQA imports it directly: you upload the Excel or CSV file you already maintain, and your cases arrive as structured test cases you can run, automate, and report on.

One upload, columns mapped for you

The friction in most imports is the mapping step: telling the tool which column means what. AxonQA does the obvious matching for you. On upload it reads your header row and lines each column up with the right field, so a column called Title becomes the case name, Steps becomes the step list, and Expected or Expected Result becomes the expected outcome. Where a header is unusual, you adjust the mapping in a single dropdown before you commit. Nothing is imported until the preview looks right, so a mislabelled column is a two-second fix rather than a cleanup job afterward.

One row per case, with steps and expected on their own lines

The format is deliberately close to how people already write cases in a sheet. Each row is one test case. Inside the steps cell, put one step per line, and inside the expected cell, put the matching expected results the same way. On import, those lines become an ordered list of steps and expectations rather than a single blob of text, so the case reads cleanly and stays easy to edit later.

• Title or Name becomes the case name that identifies the row.
• Steps, one per line, become the ordered steps of the case.
• Expected or Expected Result, one per line, become the expected outcomes.
• Priority, tags, preconditions, and a linked story id come across when your sheet includes them.

A clean round trip: export, edit, re-import

Import is only half of it. You can export any set of cases back to Excel or CSV in the same shape, which makes the spreadsheet a working surface again whenever you want one. Hand the file to a subject-matter expert who prefers a sheet, take a bulk edit offline, or reorganize a hundred cases in the tool you are fastest in, then bring the file back. The round trip is lossless: what you export is what re-imports, so the sheet and AxonQA stay in agreement instead of drifting apart.

A few things to get right before you upload

• Keep a header row, so columns can be matched by name rather than by position.
• Put one step per line in the steps cell, and keep the expected results in the same order.
• Give every case a title, since that is what each row is identified by.
• Save as .xlsx or .csv; both import the same way.

The point is to meet your team where its tests already are. If years of test design sit in a spreadsheet, you should not have to retype a word of it to get structured, runnable cases with traceability and reporting on top. Upload the file, confirm the mapping, and the library you already trust becomes the starting point for generation, automation, and everything else AxonQA does.