---
title: "Test Models"
canonical: "https://docs.getxray.app/space/XRAYCLOUD/44565545/Test%20Models"
format: markdown
---
Table of Contents
> Macro (toc)
# Introduction
A Test Model serves as your Test bench, where you define all the [parameters](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565547) and [rules](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565549). The system then uses these definitions to automatically generate all the [Scenarios](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565557).
Test models streamline the Test creation process, improve Test coverage, enable reusability, foster collaboration, and integrate with [automation](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44566603) efforts, making the overall Testing process more efficient and effective.
> ℹ️ See the full details of the Test Case Designer operations [here](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44566012).
> ℹ️
> ℹ️ Projects in Test Case Designer are a way to organize your Test Models and enable collaboration. Creating a new project does not affect Jira, so it's fully independent of your Jira Projects. You will not create a Jira Project when creating a New Project in Test Case Designer.
# Operations
> ℹ️ [Creating a Test Model](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44566012)
## Importing a Test Model from a File when Creating a New Test Model
Xray Test Case Designer allows you to import various details from your model when creating a new one. While the import feature is straightforward, it is somewhat inflexible.
You can import files in XLSX (Excel) format or OPML (Mind Mapping and Outlining).
### Importing from Excel
To import from Excel, provide a spreadsheet with a sheet named **Inputs**. Each column in the sheet should represent a parameter, and each row should contain corresponding parameter values:
| **Animals** | **Letters** | **Parameter 3** |
| --- | --- | --- |
| Monkey | A | Value 1 |
| Ferret | B | Value 2 |
> ℹ️ The spreadsheet must be in the **[Excel Workbook](https://support.microsoft.com/en-us/office/create-a-workbook-in-excel-94b00f50-5896-479c-b0c5-ff74603b35a3)** format, with an XLSX extension. To save a spreadsheet in this format, select **File → Save As**, and choose the XLSX file type.
> ℹ️
> ℹ️ To ensure the correct file format for importing, you can export an existing model or start with [this Excel example](https://designer.getxray.app/sample/Import_Template.xlsx). By following the format from an export or sample file, you can also import [constraints](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565551), value expansions, notes, and auto-scripts from their respective sheets.
### Importing from a Mind Map or Outline
Many [mind mapping](http://en.wikipedia.org/wiki/List_of_concept_mapping_and_mind_mapping_software) and [outlining](http://en.wikipedia.org/wiki/Outliner) tools support exporting to [OPML](http://en.wikipedia.org/wiki/OPML), a simple hierarchical format that can be used to define test model inputs only. To import from OPML, ensure your file name has an OPML extension.
| **Level** | **Usage** | **Notes** |
| --- | --- | --- |
| First outline level, if named with >3 characters and if they are all capital letters | Parameter Group | Optional way to group like parameters |
| First outline level, or next level under a group | Parameter name | N/A |
| Next level | Parameter values | N/A |
| Next level | Values expansions | Optional |
> ℹ️ To ensure you have the correct format for importing, compare your file with [this OPML example](https://designer.getxray.app/sample/Import_Template.opml).
> Macro (ui-steps)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
## Viewing Versions and Reverting Test Model Version (Revisions)
The Revisions option allows you to easily revert to a previous version of that Test model.
We provide a list of each revision and the date so all you have to do is click the *Revisions* button (Figure 4 - 2) to revert to that version. We also give you the option to copy that model (in case you want to view it but also want to keep all the updates you have made since then) and create a new model based on that version.
When you are editing a Test model, you will see a *Revisions* button (Figure 4 - 2) under the sub-menu of the model name dropdown .
> ℹ️ Revisions are available in editable Test Models. The *Revisions* button is not available in uneditable Test Models (such as the original sample ones).
> Macro (ui-steps)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > ℹ️ A version of a Model can be searched (Figure 5 - 3) by Label, User, and Update Details (e.g., typing *Ana* in the search field would return *Revision 2*). The Revisions feature allows a solid version control of your Test Model.
> ℹ️ See the full details of the Test Case Designer operations [here](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44566012).
Support/Troubleshooting
If you have questions or technical issues, please [contact the Support team via the Customer Portal (Jira service management)](https://jira.getxray.app/servicedesk/customer/portal/2/user/login?destination=portal%2F2%2Fcreate%2F28) or [send us a message using the in-app chat](https://getxraydocs.atlassian.net/wiki/display/XRAYCLOUD/In-App+Chat+Support).