Formatters & Code
Azure DevOps Test Case CSV Validator
Validate Azure DevOps and Test Plans CSV or XLSX test case files locally. Diagnose undefined column errors, check test steps, IDs, and preview imports.
Test case spreadsheet
or click to browse your computer (up to 10 MB and 25,000 rows)
Results
What the result means
This validator inspects your CSV or Excel (.xlsx) file against Microsoft Azure DevOps Test Plans import rules without uploading data to any external server. It groups spreadsheet rows into structured test cases, grouping repeated case fields on later step rows and flagging conflicting values. Legacy continuation rows with blank case fields are accepted, and exports repeat the case fields on each step row. If your import failed with 'Invalid/Missing value found for column(s) undefined, line 2', the tool flags empty column headings or phantom trailing columns exported from Excel. It also checks sequential step numbering, identifies unclosed HTML formatting tags in step actions, flags formula injection risks, and alerts you when new test cases and existing work item updates are mixed in the same file.
Related tools
Guides
Questions
Why does Azure DevOps report 'Invalid/Missing value found for column(s) undefined, line 2'?
This error occurs when your spreadsheet contains an empty header cell or a trailing empty column. Azure DevOps reads line 1, turns the blank header into undefined, and then fails when checking line 2. Inspect the unnamed columns, correct or remove them in the source, then validate again. Other header or mapping issues may produce a similar message.
How should multiple test steps be structured in a CSV?
Repeat Title, Work Item Type and other case fields on every step. Repeat the ID when updating an existing case; keep it blank on every row for a new case. Use sequential step numbers.
Can I update existing test cases and create new ones in the same file?
Yes, but it requires caution. New test cases must have their ID left blank, while existing test cases must have a valid positive integer ID. If an ID does not exist in your target project, Azure DevOps will reject the import.
Does this tool support Excel (.xlsx) workbooks as well as CSV?
Yes. You can upload either standard CSV files or modern Excel workbooks (.xlsx). The tool parses shared strings and cell coordinates locally and provides corrected exports in both formats.