DevOps Error: Attempting to import test cases via CSV and don't understand what this error means

Question

The error I keep getting is here below. I can't understand what is wrong and the error is labeled as undefined so it is odd.

Error message:

Invalid/Missing value found for column(s) undefined, line 2. These columns should be non-empty and should contain valid values. For more information, please refer to the help documentation: https://learn.microsoft.com/en-us/azure/devops/test/bulk-import-export-test-cases?view=azure-devops

Answer 1

Hello Serena,

The "undefined" error you are encountering when attempting to import test cases via CSV into Azure DevOps is typically caused by a corrupted header row, an unmapped mandatory field, or blank columns being parsed by the importer. When the import wizard tries to read a column without a valid header, it fails to map the object property, resulting in the "undefined" error.

To resolve this issue, you need to ensure your CSV file strictly follows the formatting and column rules expected by Azure Test Plans.

According to the official Microsoft documentation, ensure your CSV includes the exact required fields:

"Review the field mappings. The following nine fields are required:

• ID — leave empty for new test cases, or provide an existing ID to update.
• Work Item Type — must be Test Case (exact spelling and casing)
• Title
• Test Step — sequential step number (1, 2, 3)
• Step Action
• Step Expected
• Area Path — must match an existing path (for example, MyProject\MyArea)
• Assigned To — valid user in your organization.
• State — must be Design."

Troubleshooting Steps:

1. Open your CSV file in a plain text editor (like Notepad) to verify there are no hidden trailing commas at the end of your header row (e.g., ...,State,,). Extra commas create blank, "undefined" columns.
2. Ensure you do not have any blank or improperly named headers.
3. Save the file with the correct encoding. As Microsoft documentation advises: "For CSV files, save with UTF-8 encoding to preserve special characters. Enclose cell values in double quotes if they contain commas or line breaks."

Note: This response is drafted with the help of AI systems.

Answer 2

The error indicates that one or more required columns in the CSV have an invalid or empty value on line 2, but the import wizard is failing to show which column name is affected (hence undefined). The root cause is almost always one of these:

1. Missing mandatory headers or incorrect header spelling
2. Empty value in a mandatory field on that row
3. Invalid value in a mandatory field on that row

For Azure Test Plans CSV import of test cases, the file must include at least these required columns (per the import wizard):

• ID
• Work Item Type
• Title
• Test Step
• Step Action
• Step Expected
• Assigned To
• State

In addition, common validation rules include:

• Work Item Type must be exactly Test Case.
• State must be Design.
• Test Step must be a number (1, 2, 3, ...).
• Assigned To must be a valid user in the project.
• Area Path (if present) must match an existing area path.

Because the error is on line 2, that is the first data row (right after the header). The issue will be in that row.

Step-by-step to resolve:

1. Check headers
   • Confirm that all required column headers exist and are spelled exactly as expected.
   • Ensure there are no extra spaces or hidden characters in the header names.
2. Validate line 2 values
   • Open the CSV in a plain text editor (or Excel, but verify raw values) and inspect line 2.
   • Confirm:
     • Work Item Type = Test Case.
     • State = Design.
     • Test Step is a numeric value.
     • Assigned To is a valid user.
     • Any Area Path value matches an existing path.
     • No required field is blank.
3. Check for formatting issues
   • If any cell contains commas or line breaks, ensure the value is enclosed in double quotes.
   • Save the CSV with UTF-8 encoding to avoid hidden character issues.
4. Re-upload and re-run import
   • After correcting line 2, re-upload the file.
   • If the error moves to another line, repeat the same checks for that line.

If the file was exported from Azure DevOps and then edited, also ensure that ID and Work Item Type are not changed for existing test cases, and that every row for the same test case has consistent values for the non-step fields.

---

References:

• Bulk import or export test cases
• Test Plans FAQs
• Export, update, and import bulk work items with CSV files