The test nodes
- Tabs
  - Details
  - Scope
  - Results
  - Author
  - Developer
  - Dependencies
  - Attributes
  - Coverage
  - Bugs
  - Assets
  - Attachments
  - Revisions (versionning)
  - Changes (audit log)
- Toolbar

The test case nodes
- Tabs
- Toolbar

The tests

Here is a typical test tree. It immediately shows a number of useful pieces of information:

the total number of tests and testcases
the number of tests and testcases in each category
the number of tests and testcases in each folder

This screen is a bit different from the others since the left panel includes 2 separate areas:

the usual tree including all the tests that we have on the system
a sub-tree on the bottom that will list the testcases corresponding to the currently selected test

Tests can be arranged by placing them in specific folders. For instance, the tests can be organized the same way as the specifications. But if you're testing a software API, it's a common way of doing to have one test per function/method and group these functions by groups. You can then extend your test suite by adding stress test or negative tests etc. so probably need additional folders.
Tests and testcases are obviously what is the most important in the Data Model definition. The normal process is to start from specifications and make as many tests and testcases as necessary to check that specifications are all properly functioning.

Searching

For more details, please refer to the Searching objects chapter.

Importing data

If you are migrating from manual test management - using for instance a basic spreadsheet application - or another test management system to XStudio you may want to import all your tests and test cases from Excel, CSV (semi-column ';' delimited) or XML.
For more details, please refer to the thoroughly Import data tutorial.

Test vs test case

XStudio includes 2 notions: Test and Test case so it's important to well understand what it means to design properly your test plans.

A test is a group of ordered test cases.

This is at test level that you'll be able to set some dependencies with other tests
This is at test level that you can set some custom attributs (i.e. non-regression, stress etc.). Those will be very handy to build automatically your campaign later on
A Test campaign is composed of tests, not test cases. In other words, you will not be able to create a campaign and choose only some specific test cases within the same test

A Test is the unitary execution entity.

A test case is a parameterized variant of a unique scenario

Generally, a test is gathering several test cases based on the same or similar sequence of operations and verifications.
Only the parameters differ.

That said, nothing prevents from having heterogenous test cases in the same test if you think it makes sense to group them that way. The only thing to remember is that those test cases will be executed all together as the user will request the execution of the test (not the individual test cases). Anyway, all the quality metrics are provided a test, test case and even step levels.

The root node

Tabs

One of the major interests in using test management tool is the ability to trace what is covered and what is not

Specifications

To get the global tests-specifications traceability matrix (if the specifications are enabled in the settings):

switch to the Tests module on the side bar
select the root folder in the tree
on the right panel, select the Traceability Matrix tab
select the Specifications sub-tab
the test tree appears including in the right column, all the specifications covered by each test.

Requirements

To get the global tests-requirements traceability matrix (if the specifications are disabled in the settings):

switch to the Tests module on the side bar
select the root folder in the tree
on the right panel, select the Traceability Matrix tab
select the Requirements sub-tab
the test tree appears including in the right column, all the requirements covered by each test.

Bugs

To get the global tests-bugs traceability matrix:

switch to the Tests module on the side bar
select the root folder in the tree
on the right panel, select the Traceability Matrix tab
select the Bugs sub-tab
the test tree appears including in the right column, all the bugs linked to each test.

Coverage

The Coverage tab will display the coverage details of the root folder in terms of SUTs, specifications (if enabled) and requirements.
In addition, some advises are given to improve the coverage of the root folder:

Results

Progress
Tests
Test cases
Steps
Per session
Per configuration
Per agent
Per operator

The Results tab will display the results details of the tests root folder in terms of tests, test cases, steps, per session, per configuration, per agent and per operator.

To get tests root folder results:

switch to the Tests module on the side bar
in the tree, select the root folder
on the right panel, select the results tab
height tabs progress, tests, test cases, steps, per session, per configuration, per agent, per operator are displayed. Each shows some useful pieces of information:

Progress

To get progress tests results in the interval of dates:

switch to the Tests module on the side bar
select the root folder in the tree
on the right panel, select the Results tab
select the Progress tab
set the start date and end date and the SUT
for tests, select the Tests tab to display the progress of the tests
for tests cases, select the Tests cases tab to display the progress of the tests cases

Also, we can restrict the graphs to the results obtained on one SUT by selecting it on the SUT drop-down list.

Tests

To get tests results:

switch to the Tests module on the side bar
select the root folder in the tree
on the right panel, select the Results tab
select the Tests tab to display the results of the tests

In the Tests tab, we can reorder the columns, resize them, sort on the columns content, add some optional columns, create some filters and export the table to Excel.
For more details, refer to the SUT toolbar results chapter.

Test cases

To get test cases results:

switch to the Tests module on the side bar
select the root folder in the tree
on the right panel, select the Results tab
select the Test cases tab to display the results of the test cases

In the Test cases tab, we can reorder the columns, resize them, sort on the columns content, add some optional columns, create some filters and export the table to Excel.
For more details, refer to the SUT toolbar results chapter.

Steps

To get steps results:

switch to the Tests module on the side bar
select the root folder in the tree
on the right panel, select the Results tab
select the Steps tab to display the results of the steps.

In the Steps tab, we can reorder the columns, resize them, sort on the columns content, add some optional columns and export the table to Excel.
For more details, refer to the SUT toolbar results chapter.

Per session

To get the per session results:

switch to the Tests module on the side bar
select the root folder in the tree
on the right panel, select the Results tab
select the Per session tab to display the results per session.

Per configuration

To get per configuration results:

switch to the Tests module on the side bar
select the root folder in the tree
on the right panel, select the Results tab
select the Per configuration tab to display the results per configuration.

Per agent

To get per agent results:

switch to the Tests module on the side bar
select the root folder in the tree
on the right panel, select the Results tab
select the Per agent tab to display the results per agent.

Per operator

To get per operator results:

switch to the Tests module on the side bar
select the root folder in the tree
on the right panel, select the Results tab
select the Per operator tab to display the results per operator.

Attributes

Create attribute
Edit attribute
Delete attribute

The attributes are "properties" you can set on tests.
When you create some campaigns you can automatically import all the tests having certain attributes set using the filtering capabilities.

TIP: When an attribute is marked as dynamic it will be possible to overload its value for each test at execution time (set at the campaign session level).

The Attributes tab allows one to create, edit and delete attributes that may be used by any test.

Create attribute

Here is the process to create an attribute reusable for any test:

select the root folder in the test tree
select the Attributes tab and click on the create attribute button
enter the name, the type, if it's dynamic or not and optionally the normal values the attributes can take and submit
the attribute immediately appears in the panel

Edit attribute

Here is the process to edit an attribute:

select the root folder in the test tree
select the Attributes tab and select the attribute to be edited
click on the edit attribute button
change the name, the type, if it's dynamic or not and optionally the normal values the attributes can take and submit
the attribute immediately appears in the panel with new values

Delete attribute

Here is the process to delete an attribute:

select the root folder in the test tree
select the Attributes tab and select the attribute to be deleted
click on the delete attribute button
confirm and submit
the attribute immediately disappears from the panel

Params

Create param
Edit param
Delete param

The params can be seen as "variables" you can use in your test cases.
You can use params in the descriptions (or procedures) of your test cases by just typing the param name surrounded with %
Param values can be set either manually on each test case or generated automatically by one of the combination algorithms when creating a new test case template.

For instance, if you insert %browser% in a test case description, it will be replaced at execution time with the value of the browser param set on this specific test case (i.e. Firefox).

TIP: It is possible to globally overload all the values of a specific param (on all the testcases) at execution time with a forced value (set at the campaign session level).

The Params tab allows one to create, edit and delete params that may be used by any test case.

Create param

Here is the process to create a param reusable for any testcase:

select the root folder in the test tree
select the Params tab and click on the create param button
enter the name, the type, the normal values for this param, optionally some invalid values and submit
the param will immediately appears in the panel

Edit param

Here is the process to edit a param:

select the root folder in the test tree
select the Params tab and select the param to be edited
click on the edit param button
change the name, the type, the normal values for this param, optionally some invalid values and submit
the param immediately appears in the panel with new values

Delete param

Here is the process to delete a param:

select the root folder in the test tree
select the Params tab and select the param to be deleted
click on the delete param button
confirm and submit
the param immediately disappears from the panel

Statistics

The Statistics tab will display some metrics based on all the tests and test cases in the tree:

A priority breakout bar chart showing how many tests exist for each priority
A number of test cases breakout bar chart showing how many tests have how many test cases (in different ranges 0-5, 6-10, etc.)

Custom fields

Create custom field
Edit custom field
Delete custom field

You can customize the tests and the test cases by creating some new custom fields that will appear in their Details tab.
Custom fields can have different types: text fields, drop-down menu, checkbox, formatted text field. They can also be marked as mandatory or not and are positionned at the index you specify.
The Custom fields tab includes tco sections (one for the tests and one for the test cases) allowing to create, edit and delete custom fields.

Create custom field

Here is the process to create a custom field for a test:

select the root folder in the tree
on the right panel, click on the create custom field button
enter the name, the type, the position, if it's mandatory or not and the default value of the custom field and submit
the custom field will immediately appears in the panel
the new custom field is added to all the tests assigned with its default value

Edit custom field

Here is the process to edit a custom field for a test:

in the tree, select a root folder
on the right panel, select the custom field
click on the edit custom field button
change the name, the type, the position, if it's mandatory or not and/or the default value of the custom field and submit
the custom field immediately appears in the panel with new values
the custom field is updated on all the tests

Delete custom field

Here is the process to delete a custom field for a test:

select the root folder in the tree
on the right panel, select the custom field
click on the delete custom field button
confirm and submit
the custom field immediately disappears from the panel
the custom field is removed from all the specifications

Here is a schema that sum-up the differences among attributes, params and custom fields:

Toolbar

Create a category

This first thing to do is to create a category. To do this:

in the tree, select the root folder
on the right panel, click on the create category button
a dialog box is displayed
enter the name of the category.
enter the description of the category. You can use the formatting tools (wiki-style) to format the text.
choose a launcher to be associated with that category: tree_step_manual.jar (one of the 5 different interfaces for manual testing) indicates that all the tests included under that category will be executed using the tabular manual test launcher.
click on submit
the category immediately appears in the tree

Create a report

It may be interesting to export or to print a global report on all the tests you have.
For more details, refer to the Tests report chapter.

The category nodes

Tabs

Details

The category details tab allows one to specify the name, the descripton of the category and the type of Laucher.
For manual testing, there is four different Manual lauchers:

Manual
Simple manual
Tabular manual
Tabular step manual

For more details, refer to the Manual launcher chapter.