Skip to main content

Export

QA Sphere allows exporting test case library in CSV (Comma-Separated Values) format. To do that:

  1. Open a project and go to Test Cases tab
  2. Click three dots
  3. Select Export

A new CSV file with the project abbreviation in the name will be saved under the browser's downloads.

The structure of the exported CSV file columns are as follows:

Static Columns:​

  • Folder: The complete folder path to the test case
  • Type: The type of test case - standalone or template
  • Name: Title of the test case
  • Legacy ID: Test case ID from previous test management system
  • Draft: Whether the test case is a draft (true or false)
  • Priority: Test case priority - low, medium, or high
  • Tags: Comma-separated tags
  • Requirements: Comma-separated requirements in format [Title](URL)
  • Links: Comma-separated links in format [Title](URL)
  • Files: JSON array containing file information with properties: fileName, id, url, mimeType, size
  • Preconditions: Test case preconditions or description (in Markdown format)
  • Parameter Values: JSON array for template test cases containing parameter sets
  • Template Suffix Params: Comma-separated parameter names used in filled test case naming

Dynamic Columns:​

After the static columns, there are dynamic columns for:

Steps​

  • Step 1, Expected 1
  • Step 2, Expected 2
  • ... (continues based on the maximum number of steps in any test case)

Custom Fields​

Custom fields appear after step columns with the format:

  • custom_field_text_{systemName} for text fields
  • custom_field_dropdown_{systemName} for dropdown fields

Custom field values are exported as JSON objects containing:

  • value: The field value
  • isDefault: Whether this is the default value (if applicable)

Export Format Details​

Column Organization:​

  • The number of "Step" and "Expected" columns is determined by the test case with the most steps
  • All rows are padded with empty values to match the maximum number of steps
  • Custom field columns are included only if custom fields exist in the project
  • Rows are sorted first by Folder name, then by test case Title within each folder

Data Formatting:​

  • HTML to Markdown: Content in preconditions and steps is converted to Markdown format
  • Template Test Cases: Exported with their parameter values and template configuration
  • File Attachments: Exported as JSON with complete metadata for re-import
  • Custom Fields: Exported with their current values and default status

Template Test Cases in Export:​

When exporting template test cases:

  • The template definition is exported with Type set to template
  • Parameter values are included in the Parameter Values column
  • Template suffix parameters are preserved for consistent naming on re-import
  • Filled test cases generated from templates are exported separately as standalone test cases

This comprehensive structure allows for:

  • Complete backup of test case libraries including custom fields and templates
  • Migration between QA Sphere projects
  • Integration with external tools that support CSV format
  • Preservation of all test case metadata and relationships