Hi @Kishore Chava , It looks like you're having trouble importing test steps while importing test cases from Excel. This can happen due to some specific requirements and limitations within Azure Test Plans.
Here’s what you can check:
- Mandatory Fields: When importing test cases, ensure that your Excel sheet includes all the mandatory fields. You need at least these nine headers to be correctly defined:
- ID (leave empty for new cases)
- Work Item Type
- Title
- Test Step
- Step Action
- Step Expected
- Area Path
- Assigned To
- State
- File Format: Make sure the Excel file is saved in the correct format (XLSX) and that it doesn’t exceed size limitations. The data during import should not exceed 20 MB as JSON objects.
- Restrictions on Test Steps: It’s important to know that if you included both a shared step reference and step details in the same row, this may cause the import to update the existing shared steps work item. If you want to just reference shared steps without modifying them, make sure not to include step details in that row.
- Import State: Ensure that the test cases are in the “Design” state during the import process.
- Review Field Mapping: After you upload your file, double-check the proposed field mappings to ensure everything is automatically mapped correctly.
If you're still stuck, please share below information to troubleshoot further:
- What specific error message are you encountering during the import?
- Can you confirm that your Excel file has all the required fields filled out correctly?
- Are you using the updated import interface, or are you on the legacy interface?
- Have you tried importing a smaller subset of test cases to see if that succeeds?
Hope this helps you get things moving again! If there's anything else you need, feel free to ask!
References:
- Bulk import or export test cases
- Run automated tests from test plans
- Test Management REST APIs
- Test suites context menu options explained
Note: This content was drafted with the help of an AI system.