Skip to content

Import test cases from Excel

In the Windows project tree, select the test library or destination test unit. Open its context menu and select the Excel import command under Import/Export.

Choose the source file, worksheet or named range. If the first row contains column headings, enable that option. Check the preview, map the source columns to the destination fields and follow the wizard to completion.

Import quick test cases

For quick test cases, one source column identifies which spreadsheet rows belong to the same case.

Use this example spreadsheet. Rows with group A belong to case A; rows with B or C belong to cases B or C.

Group Step Type Area
A Sign in Function Customer portal
A Sign out Function Customer portal
B Open order Function Orders
B Filter by status Function Orders
C Export Excel Function Reporting
C Check file Verification Reporting
  1. Map Group to the test case's title.
  2. Select Group as the source quick grouping field.
  3. Map Step, Type and Area to the corresponding fields under Quick rows. Those fields come from the quick style used for the destination.
  4. Complete the import and read the completion message.
  5. Open the three imported cases and check that each contains its two expected rows.

Select the grouping field before connecting the quick-row fields, so that the mappings retain the intended group.

Moving from another test tool with attachments and dependencies

This import is available in the Web client in the current development build. In the Test library, open the import menu and choose Import from another test tool. You need permission to create cases in the target test unit. To try the import, download the sample workbook and its attachment ZIP. The sample contains two cases with the same name and different IDs, two attachments (TXT and PNG), and one dependency.

  1. Prepare your source export as an XLSX workbook using the sheet and column names below. Keep the original stable case IDs, including for cases with identical names. Store IDs with leading zeros as text.
  2. Enter a stable source identifier for the original tool and source project, select the target test unit and upload the workbook and optional ZIP. Select Review import. The preview shows new cases, unchanged cases, conflicts and omitted data without saving anything.
  3. Review the messages and select Import reviewed package. Resolve any blocking messages before importing. Open an imported case to inspect its project attachments. The dependent case lists its prerequisite as an informational dependency.
  4. Use the same source identifier and target test unit on subsequent imports. The importer recognizes identical cases and files. Changed source data, local edits or an existing case with a matching name but no matching source identity block the whole package. Existing cases are not overwritten; review the affected data before creating a new preview.
Sheet Columns and content
Cases ExternalId and Name are required. Optional columns are FolderPath (e.g. Shop/Prüfung), Description, Prerequisites, Steps and ExpectedResult. Supply descriptions as plain text. A package can contain up to 500 cases.
Attachments CaseExternalId and Path. Each path identifies a file inside the ZIP, e.g. evidence/image.png. Include pictures as files.
Relationships FromExternalId, ToExternalId and Type. For depends-on, the dependent case points to its prerequisite. Both IDs must be in the package.

The Web form accepts up to 10 MiB XLSX and 20 MiB ZIP; a single expanded file can be up to 16 MiB. A package supports up to 500 attachment assignments and 2,000 dependencies. Formulas, external links, missing files and invalid references block the import.

The preview reports result history, unrecognized sheets or columns, embedded workbook images and annotations as omissions. Reference pictures through Attachments and include them in the ZIP to import them. Custom fields on an Attributes sheet (CaseExternalId, Name, Value) block the import; this workflow does not yet provide field mapping. Keep the original export if you need to retain this information.

If the project is busy, the reviewed preview remains available. End other project access and select Retry import while the preview is valid. You do not need to upload a corrected package. A saved import receipt is checked and returned on retry without creating further copies.