Skip to main content

Library/Tests

Tests & Library​

An assessment is comprised of a number of different entities. One of the main entities is the Test. Tests are the components used to evaluate whether specific criteria are met. Each test is designed to assess a particular aspect of the criteria defined within a Motivation.

info

We have to mention here that the actions described below are for an admin user.

Manage Tests​

To manage Tests, a user should navigate to the Library / Tests tab from the Personal Menu located on the left sidebar in the section Library. In this page, the user can find the list of Tests supported by the service.

Creating a New Test​

To create a new test, the user should click the Create New button which will redirect them to the Test modal screen.

Creating a New Test

On the creation page, users must provide key details about the test.

The required information includes:

  1. TES (required): A unique identifier assigned to the test, ensuring it can be distinctly referenced within the service.
  2. Label (required): A label describing the Test. It should be unique and easily recognizable to avoid confusion with other tests.
  3. Description (required): A small description of the Test.
  4. Test Method (required): Select the appropriate test method for the test.

Additionally, there are optional parameters and evidence that can be added:

  • Parameters: Click Add new to create parameters that define specific inputs or conditions for the test.
  • Evidence: Click Add Evidence to attach supporting evidence related to the test.

Once the necessary fields are filled in, the user can click the Create button to create the test and will be redirected to the page with the list of tests. If the user wishes to cancel the process, they should click the Cancel button.

Edit a Test​

A user can edit one of the tests by clicking on the Edit test button.

Edit a Test Button

Then a modal like the one in the following image will appear.

Edit a Test

The user can update the following fields:

  1. TES (required): A unique identifier assigned to the test.
  2. Label (required): A label describing the test.
  3. Description (required): A small description of the test.
  4. Test Method (required): Select the appropriate test method.

Additionally, the user can update Parameters or Evidence as needed by clicking on the respective buttons to add, edit, or remove them.

Once the necessary fields are updated, the user can click the Update button to save the changes and will be redirected to the page with the list of tests. If the user wishes to cancel the process, they should click the Cancel button.

Delete a Test​

A user can delete one of the tests by clicking on the Delete test button.

Then a modal like the one in the following image will appear.

Delete a Test

warning

If a Test is already in use, deletion is not allowed.

The user can click the Delete button to delete the test and then will be redirected to the page with the list of tests. If the user wishes to cancel the process, they should click the Cancel button.

View a Test​

A user can view one of the tests by clicking on the View test details button.

Then a modal like the one in the following image will appear.

View a Test

In the View Test modal, the user can review the test details, including parameters and evidence.

Test Versioning​

Understanding Test Versions​

Test versioning allows you to maintain a history of changes made to a test, ensuring that previous versions can be accessed, and modifications are tracked. When a test changes, a new version is created, which helps in maintaining the integrity of the assessment process over time.

Viewing and Managing Test Versions​

  1. Viewing Versions:

    • When you view a test, you will see the latest version by default. If multiple versions exist, you can navigate to the version list to see all past versions.

  2. Creating a New Version:

    • When a test changes and a new version is created, it will automatically be added to the list of versions for that test. The versioning process helps in tracking changes over time.

  3. Deleting a Test with Versions:

    • If a test has multiple versions, it cannot be deleted. If you wish to delete a test, ensure that no versions exist or that the test is not in use by any motivations.

Key Rules for Test Versioning​

  1. Tests Used in Motivations Cannot Be Deleted:

    • If a test is used in any published motivation, it cannot be deleted. This ensures that no active motivation is broken due to the removal of a test.

  2. Tests with Versions Cannot Be Deleted:

    • If a test has multiple versions (i.e., version 1 and later versions), the first version (version 1) cannot be deleted if any subsequent versions exist. This is to preserve the history and avoid accidental removal of a foundational test.

  3. Displaying Test Versions:

    • The system displays the most recent version of a test first. All previous versions are listed as children under the latest version for transparency and historical tracking.

  4. Test Name Remains the Same Across Versions:

    • The name of a test remains consistent across all versions to avoid confusion and ensure that tests can be easily referenced by their common name, regardless of which version is being accessed.