Page History
...
A Test Model is your test bench, where you define all the parameters, and rules so that the system can then generate all the scenarios and test scripts automatically. In this section, we will go through the basic steps to create/copy your test models.
...
| UI Steps | |||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||
|
| Tip |
|---|
Want to understand how to create a test model? Explore our Test Models samples. |
...
Xray Test Case Designer allows you to import all types of details you might have in your model. The import feature is straightforward but fairly relatively inflexible.
You can import from .xlsx ( MS Excel) or from OPML (Mind Mapping & Outlining).
...
Provide an Excel spreadsheet with a sheet named Inputs. Each column in the sheet is a parameter, and each row has parameter values:
...
| Info |
|---|
To ensure you have the correct file format for importing, export an existing model , or start with this Excel example file. If you follow the format from an export or this sample, you can also import constraints, value expansions, notes, and auto-scripts from their respective sheets. |
...
Many mind mapping and outlining tools support exporting to OPML, a simple hierarchical format that can only be used to define test model inputs only. To import from OPML, ensure your file name has a .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 | |
| Next levelLevel | Parameter values | |
| Next levelLevel | Values expansions | Optional |
...
| UI Steps | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
Make a Copy of an Existing Test Model
| UI Steps | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||
|
A couple of things to note:
“Model name” of the copy will just add “(copy)” to the original by default , but can be changed as long as it is unique in a given project or the private collection.
Project The project name has to be filled in and should be a unique per-user account (i.e., another user can have a different project with the same name).
The “Revision History” checkbox allows you to preserve the traceability of edits across plans. However, for old plans, it may be better to clear the history for faster performance for old plans.
The “Switch” checkbox allows users to instantly start working on the copied version instantly. Uncheck it if you create something for the future needs and are not ready to edit it yet.
...
| UI Steps | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
View Version and revert the Test Model version (Revisions)
The Revisions option allows you to easily revert to a previous version of that test model easily.
We provide a list of each revision and the date, so all you have to do is click a button to revert to that version. We also give allow 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.
...
| Info |
|---|
Revisions are available in editable test models, ; the revisions link is not available in un-editable uneditable test models (such as the “original” sample ones). |
For each revision, three options are available:
...
A version of a model can be searched for by Label, User, and Update Details (e.g., typing “Java” in the search field would return “Revision 2”). The Revisions feature allows a solid version control of your test model.
Revert a Test Model version.
To revert, click the Revisions link, and a list of all versions of the model is displayed:
...
Fill in the details of your note and click the “Create” button. Keep in mind Remember that anyone with access to the plan (including reviewers, etc.) can use this feature. This is usually a good thing.
If you need more context for a note, it may be useful helpful to check the Revisions under the plan name dialog.
...
| UI Steps | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
Share a Test Model
First, open the model from the project that you would like to share. Next, click on “Share” underneath Review in the left navigation pane.
...
| Info |
|---|
If the plan is not yet in a project, you will first need to move it to a project. If You can skip this step if the plan you are sharing share is already in a project, you can skip this step. Please note that all of the plans in the project will be shared because sharing is done by the project, not by individual plan. |
...
The email address field will present the list of users from your organization upon a partial match.
As explained in the table below explains, you can select different usage rights based on your preferences.
...
When sharing with someone who is not yet familiar with how to use Xray Enterprise Test Case Designer, you might want to select “Can Copy and Comment on Plans.” That way, the person you share with will be able to make comments to comment on your plans and ask clarifying questions about itthem, but they will not be able to make changes to your plan.
...
After you have designed your test model, you can synchronize it to Xray so that you can then to track test execution.
| UI Steps | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
|
To keep track of synchronizations, access the "Sync History" on the screen to track all synchronizations as well as its their status:
| Tip |
|---|
To better track the issues created on Jira, the system will add labels to issues with the test model ID and with a generic label to tag the issues synched from Xray Test Case Designer.
|
