如何在TestLink工具中导入Excel表格？按要求准备后仍无法添加

Hey there, let’s work through this TestLink Excel import issue together—since you already stuck to the step/action/expected result/execution status format, we can zero in on the easy-to-miss details that often cause this problem.

Common Fixes to Try #

• Stick to the right Excel format
  TestLink plays nicest with Excel 97-2003 (.xls) files, not the newer .xlsx format. Even if your file looks correct, saving it as .xls can resolve hidden formatting glitches. Also, no merged cells allowed—they break TestLink’s row/column parsing logic every time.
• Double-check header matching
  Even if you used the required headers, make sure:
  • Your headers match TestLink’s expected labels exactly (yes, case sensitivity can matter here—match the case shown in TestLink’s built-in import template if you have it).
  • There are no extra, unused columns in your file. TestLink gets confused by unexpected columns, so delete any that aren’t part of the step/action/expected result/execution status structure.
• Clean up your data
  • Watch for special characters like #, &, or hidden line breaks in test steps—these often trigger parsing errors. Replace or remove them.
  • Ensure your "Execution Status" values are exactly what TestLink accepts: Passed, Failed, Blocked, Not Run—no typos like pass or Fail (capitalization counts here too).
• Verify import settings in TestLink
  When you start the import:
  • Pick the correct test suite or folder to import into. If the target doesn’t exist, or you don’t have edit permissions for it, the import will fail without a clear message.
  • Choose the right import mode: "Create new test cases" if you’re adding entirely new ones, or "Update existing" only if you’re modifying cases that are already in TestLink. Mismatching these can cause conflicts.
• Remove empty rows and extra headers
  Delete any blank rows at the top, bottom, or between test cases. Also, make sure your header row is the very first row—no title rows or blank lines above it, because TestLink starts parsing from row 1.
• Test with a minimal file
  Create a tiny test file with just 1-2 simple test cases, following the exact format. If this imports successfully, the problem is in your original file’s data (not the format itself). Add more cases one by one to find which row is causing the failure.

Pro Debug Tip #

If TestLink throws an error message (even a vague one), don’t ignore it—it usually points directly to the issue. For example, "Invalid execution status in row 5" tells you exactly which row needs fixing.

内容的提问来源于stack exchange，提问作者Rakesh Gajarmal