Data Exports
It is possible to schedule and generate exports of your data from your Testmo instance under Admin > Exports. Once you schedule a data export, Testmo exports your instance data to a JSON file and provides a download link from the Exports page. Depending on your instance database size, it can take a while until the download is ready. New data exports can be scheduled once per day.
Scheduling data exports

Working with data exports

We designed and developed Testmo's data export feature for a few specific scenarios and use cases:
  • Importing into BI/reporting tools If your organization is using third-party BI/reporting tools, you can use Testmo's export files to import your testing data and generate additional custom reports or dashboards.
  • Build custom integrations If you would like to build custom integrations with other tools, you an use the export files to automate certain tasks such as synchronizing test cases or test results with other systems.
  • Additional disaster recovery backups You can use the data exports to make additional internal backups of your testing data as part of your disaster recovery plan and your internal data backup policies. Note: data exports can be used as an additional backup to retain access to your data in case of service interruptions. But data exports cannot be imported/restored into a Testmo instance (see below).
  • Migrating data to another tool If you for whatever reason decide to move to another tool in the future, we want to make it easy to take your data with you. You can use the export files to migrate your test cases, results and projects to another tool.
There are also a few limitations of the data exports and scenarios we do not currently support:
  • Importing data exports into Testmo It is not possible to import or restore an existing data export into a Testmo instance. The generated JSON files do not contain all data links and relations that would make them suitable as full database imports or to restore a full Testmo database.
  • Exporting file attachments Due to size limitations and scalability considerations, we do not currently include attachment files and uploads in data exports.

JSON file format

The data exports are provided as JSON files. JSON files are supported by most systems and are easy to process and read with any programming language, so you can build your own processing scripts or import the data exports more easily.
We include all important data entities in the export files such as test cases, results, sessions, projects, users etc. For each entity and data table we include a separate section with the schema description and the data.
The following example provides a small excerpt of a data export showing the export of test cases (note that we reduced the number of fields for this example to make it easier to read; the full data exports include more fields):
1
{
2
"repository_cases": {
3
"schema": {
4
"id": "id",
5
"key": "id",
6
"project_id": "id",
7
"folder_id": "id",
8
"template_id": "id",
9
"name": "string",
10
"state_id": "id",
11
"estimate": "uint",
12
"forecast": "uint",
13
"display_order": "uint",
14
"created_at": "timestamp",
15
"created_by": "id",
16
"custom_priority": "mixed"
17
},
18
"data": [
19
{
20
"id": 1,
21
"key": 1,
22
"project_id": 1,
23
"folder_id": 1,
24
"template_id": 3,
25
"name": "The first test case",
26
"state_id": 4,
27
"estimate": null,
28
"forecast": null,
29
"display_order": 1,
30
"created_at": "2021-11-29 13:16:02.295870",
31
"created_by": 1,
32
"custom_priority": 2
33
},
34
{
35
"id": 2,
36
"key": 2,
37
"project_id": 1,
38
"folder_id": 1,
39
"template_id": 3,
40
"name": "The second test case",
41
"state_id": 4,
42
"estimate": null,
43
"forecast": null,
44
"display_order": 2,
45
"created_at": "2021-11-29 13:16:07.821261",
46
"created_by": 1,
47
"custom_priority": 2
48
}
49
]
50
}
51
}
Copied!
The schema section lists all fields and their types for data included for the relevant entity. Testmo currently uses the following fields for data exports:
  • bool
  • id
  • int
  • mixed
  • string
  • text
  • timestamp
  • uint