Skip to content

Attributes

Attributes are name value pairs that can be attached to different elements within the hierarchy of a project (e.g. to test cases). Attributes can also be inherited from parent hierarchy elements to child hierarchy elements.

Attributes are therefore a general purpose functionality of Zeta Test to add additional information (in the form of name value pairs) to existing elements.

Note

Attributes are a completely optional feature. For most of your Zeta Test projects, it is very likely that you never need to use attributes at all.

Once attached to an element the attributes are, among others, accessible in the following contexts:

  • In reports.
  • In the tabular content area of the main window.
  • In the "Overview" tab in the content area of the main window.

Attribute types

Besides a name and a value, attributes can also be given a type. The type controls how the user enters values for an attribute and how values entered are then displayed.

The types available are:

  • Text box, single line
  • Text box, multi line
  • Date selection
  • Check box
  • List

Attribute styles

Attribute styles are an advanced feature with which you can define a template of "attributes to create" that can be used later in the workflow.

An attribute style contains one or multiple style fields that define the name and type of the attributes that are being created based on that attribute style.

In the Web client, open Project settings → Attribute styles. Each style shows its field count and usage count below its name. Click a row to select only that style and see its fields. Use the checkboxes to select multiple styles. In the field editor, Promoted marks a field for display on the first tab.

Defining and assigning attribute styles

To create, edit or delete attribute styles, follow these steps:

  1. On the Manage ribbon, select Attribute styles. → The "Attribute styles" dialog window will open.
  2. On the "Attribute styles" tab, use the button "New", "Edit" or "Delete".

You also can define standard attribute style for the various element types in the structure view of the main window. When being defined, these styles are available in the property dialog windows of the elements on the "Attribute" tab, in the context menu of the "New" button.

To define standard attribute styles follow these steps:

  1. On the Manage ribbon, select Attribute styles. → The "Attribute styles" dialog window opens.
  2. Click on the "More settings" tab.
  3. For each element listed, select the standard attribute style.

There is another input method for attributes, used for entering attributes for test cases, as well as during a test run.

In these scenarios, attributes cannot only be created on the "Attributes" tab, but also listed side-by-side on the very first tab of the dialog window. This simplifies entering of attributes for the users.

To configure an attribute to be enterable on the first tab page, you have to mark the respective attribute style as being a "promoted attribute".

To do so, follow these steps:

  1. On the Manage ribbon, select Attribute styles. → The "Attribute styles" dialog window will open.
  2. On the "Attribute styles" tab, use the button "New" to create a new attribute style, or use the button "Edit" to edit an existing attribute style.
    → The "Edit attribute style" dialog window will open.
  3. Use the "New" button to add an attribute style field. →The "Edit attribute style field" dialog opens.
  4. Set the value of the field "Is promoted" to "Yes" in the "Settings" field.
  5. Close all dialog windows with "OK".

After these steps, it is important that you assign the respective attribute style as a standard attribute style for test cases or test run result items. Otherwise Zeta Test cannot detect which attribute style to use for displaying promoted attributes.

Note

Be careful when configuring promoted attributes to ensure that you changes do not erroneously change already finished test runs.

Checking field assignment and origin

In the Web client, open Field assignment below a promoted field or beside an attribute name. The details distinguish an own value, an inherited value and an unsaved field default. They identify the field ID, style, field type and the kind and ID of the object storing the value. Free attributes and missing field definitions are marked explicitly. The style-field editor also shows the style and existing field IDs.

In Windows, select an item on the Attributes tab and open Field and source. Details are available for read-only values as well. For promoted fields, the corresponding button shows the displayed fields' assignments; style and field editors show their IDs.

Two equally labelled style fields are not automatically the same input field. Two different origin rules apply:

  • Attribute list: Own values take precedence. Inheritable values from parent objects are combined by case-insensitive name. A nearer attribute of the same name hides more distant values, even when the nearer attribute is not inheritable itself.
  • Promoted input field: It shows the own value for the specific field ID or the field definition's default. It does not use an inherited attribute merely because its name matches. This keeps a tester's own result input separate from a library value.

Following imported values through planning, results and reports

  1. Choose the default style intended for test cases and map the import column to the appropriate field. Check its name, type and ID and the actual destination folder. A test-unit style is not automatically the style for its test cases.
  2. Check the imported value on the library test case. Adding it to a plan template copies its own attributes to the planned test case. This is not a live link: later library changes require explicit synchronization; frozen definitions remain protected.
  3. While testing, distinguish an inherited value in the attribute list from a promoted result input. Result attributes can originate from the planned test case; planned variant values do not provide an additional automatic inheritance path.
  4. Check the intended report. Supported reporting data includes effective attributes, but the selected template must display them. Not every report automatically shows all custom fields.

A test run is a parent of its planned test cases. Their values are not copied upwards into its attributes. New assignments do not automatically overwrite own result values or historical or frozen copies.

Checking Excel mappings before import

The Windows wizard matches the name and, when supplied, field type within the actual test-case default style. Without a default style, an existing match must be unique across all styles. Missing fields are created in the intended import style. Preflight also checks destinations from hierarchy columns and stops on ambiguity before creating folders or cases.

In Web, select a specific destination field; choices also show its style, type and ID. Duplicate names are not silently mapped automatically. Deleted fields, conflicting mappings or different destination styles in the imported hierarchy must be corrected before starting. Split the import by destination style when necessary. A failed preflight writes no import data; cancelling an already running import can still leave previously imported rows.