Overview

Test Case Designer provides an administration area where administrators can manage your organization’s Test Case Designer instance and user permissions.

Access and Navigation

Managing User Authentication Settings

From the Organization Settings screen (Figure 3 - 1), the User Authentication Settings screen (Figure 3) allows you to select and edit the authentication method (Figure 4 - 1), by clicking User Authentication Settings (Figure 3 - 2).

Figure 3 - Users

Once you're finished editing the authentication settings, click Update Organization (Figure 4 - 1).

Figure 4 - Authentication

User Management

Setting Permission Levels

There are two permission levels:

• Edit (Figure 3 - 4).
• Read-only (Figure 3 - 5).

They have separate limits from the licensing standpoint, which can be seen in the Organization Settings screen (Figure 3).

The following rules apply when dealing with the seat limit:

• New self-registered users default to the Edit level if the seats are available and to Read-only otherwise.
• When a customer administrator tries to register an edit-level user while the number of edit-level seats for the organization has been exhausted, the red tooltip will display, and clicking Register User will require confirmation for Read-only switch.
• Blocked users do not count towards seat limits.

Within license limits, you can set the permission level per user at Edit Permissions or for the whole organization using this checkbox column (Figure 5 - 1). 

• If the checked the user has Edit permission.
• If unchecked the user has Read-only permission.

(Checked = Edit seat/Unchecked = Read-only seat):

Figure 5 - Permissions

Read-only Limitations

• The option to create a new model and export an existing one will be shown but disabled. Users will get a warning when trying to access them.
• Parameters, Rules, and Scripts will be available for review only and disabled for editing.
• Scenarios will be available for review for any pre-calculated strength but disabled for generating a new set.
• Commenting options (notes) will be available and fully functional.
• Sharing options will be disabled. From the perspective of inviting a read-only user to the project, they cannot be promoted to edit at the project level.

Setting the Administrator Role

In the Actions column in the table, you can use the green icon (Figure 5 - 2) to designate someone else as the Admin (in which case they can perform all the actions at the Administration Panel) or revoke such privileges.

Disabling/Enabling Users

The read icon (Figure 5 - 3) is for disabling users – either for the reason of license seat limitations, for them leaving the company, or for any other reason. You can choose to enable those users later – they will keep all their assets intact.

Managing Email Domains

You can edit the email domains associated with the access to your organization. 

Inviting a User

Managing Export Configurations

You can access the export configuration screen by clicking the Customize button (Figure 10 - 3).

Figure 10 - Customize

This screen (Figure 11) provides two main options/tabs:

Export Configurations

Here (Figure 11 - 1) you can manage the export configurations.

Figure 11 - Configuration

At this step, you just need to decide on the configuration name. You can update the default options to match your needs, but we generally recommend keeping them for reference purposes.
You can have multiple configurations for the same target export if, e.g., teams have diverse options for relevant metadata columns.

Once you're done, click Update (Figure 11 - 2) to make the changes effective. You can also click Delete to remove the respective configuration (Figure 11 - 3).

Export Fields

Here (Figure 12) you can manage the field configurations, their format, and potential values.

Figure 12 - Fields

Edit Export Fields for (Figure 12 - 2) selects the Export Configuration to manage the fields.

The Script Type dropdown (Figure 12 - 1) allows you to select whether this configuration can apply only to Manual scripts, only to Automate, or to both.

Each field can be made mandatory or optional using the second column with the checkboxes (this will not affect the export of fields populated automatically). Finally, you can reorder fields using the indices in the first column (Figure 12 - 2).

There are three field types available (Figure 12 - 5):

• • Populated automatically – depending on your scripting in Test Case Designer (Manual or Automate), certain core elements like Step Description or Gherkin Scenario Steps will be pulled from the source and will not be editable in the export dialog itself.
    • Alternate Name allows changing the displayed column name after export, which can make the mapping setup for Test management tools easier.
    • Naming Convention and Example for the Test Name can provide the template tooltip for syntax rules.
  • Text – a fairly standard string field that can be left blank or specified with the default value.
  • Dropdown – can handle the single selection with the options separated by commas (you can refer to the tooltips in the 4th column header for syntax guidance).
    
    

Once you're finished editing a field, click Update to make the changes effective (Figure 12 - 3).

You can add a new export field by clicking Add (Figure 12 - 4).