Test objects

Table of Contents

Test objects are subordinate to the individual test object types. They can be linked hierarchically and thus play an important role in data analysis. Test objects are the objects that actually exist, where issues can occur and checklists are needed for maintenance or similar purposes.

Add a new test object

Adding a test object to a test object type can be done by clicking the orange button in the right lower corner in the respective test object type overview. When you create a test object, you can define the following characteristics:

  • Identifier: The identifier uniquely identifies a test object and can take over the identification numbers which are already in use.

  • Title: The title describes the test object and is used as identifier in any listing or search.

  • Description: The description supplements the title with other important information about the test object.

  • Details: The details contain the added custom fields which have been defined in the test object type. Various input values can be added to the test object directly or automatically via an interface (API).

  • Parts List: Selects the appropriate elements for a test object in order to be able to locate the issue more precisely when recording issues. Improves data analysis.

Editing test objects

After creation of the test object it can be edited by clicking on the context menu (the three dots) in the upper right corner of the test object overview. All informations from above can be edited.

Linking test objects (test object hierarchy)

After test objects have been created, they can be hierarchically linked to each other in the “Components” section of the test object in order to display the dependencies. If you want to add a subcomponent to a test object, you have to select the orange button in the right lower corner of the corresponding test object under link subcomponent. Once this is done the subcomponent and the master component are displayed in the “Components” area. During data analysis, you can now filter and localize the subordinate subcomponents using a master component.

Disable test objects

Testify admins can disable test objects via the administration area. To do this, first select the corresponding test object type and then click on Test objects to display the test object view.

Disabling is possible via two variants, each by clicking on the context menu (the three dots).

Disable via the test object overview:


Disable via the test object:

When disabling, some setting options appear in advance to define whether the associated issues, checklists and subcomponents of the test object should also be removed/disabled.

In addition, if "Disable subcomponents" has been clicked, it is possible to select whether the issues and checklists of the subcomponents should be removed.

The components can be shown up in advance via the "Components" button to ensure which issues, checklists as well as subcomponents are assigned to the test object.

After deactivation, the "Disabled successfully" display appears and the overview turns gray.

Depending on the settings made previously, the associated checklists, issues (if any) and subcomponents can now be seen here.

Activating test objects

Reactivating test objects is possible in the same way as deactivating them, in each case via the context menu.

Activate via the test object overview:

Activate via the test object:

When activating, you can select whether the subcomponents should also be reactivated.

When successfully activated, the "Updated successfully" display appears.

Export and import of data

Inserting data is possible either directly in Testify by manual creation or by export/import. For more on export/import: https://testify.atlassian.net/wiki/spaces/TWN/pages/1507229936