---
sourceDocument: Yokohama Proactive Service Experience Workflows
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/proactive-service-exp-workflows

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Proactive Service Experience Workflows

ft:clusterId :

    - psew

bundleId :

    - psew

workflow :

    - Customer and Industry


---

# Setting up test definitions

# Setting up test definitions {#ariaid-title1}

Release version: Yokohama  
Updated January 30, 2025  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Define tests for a particular service type, product model, or inventory to troubleshoot the service-related problems.

Test definition includes characteristics, relationships, test measures definitions, measure consequences, and threshold rules. These entities enable the system to trigger relevant tests for the service problem that help to identify the
root-cause of the problem. You can define these entities for each test based on your requirements.

A service test definition outlines the parameters to be configured and the metrics to be measured for a given service test. These parameters are defined in the test definition. They can be set during execution to run the tests that
measures the service problem effectively. This structured approach ensures that the test is done correctly and collects all the data needed to identify the problem of the service.
* **[Create a test definition](https://servicenow-prod.fluidtopics.net/VVoXcDpc8LrK031MgkP0JA)**   
  Create a test definition to define tests that can help troubleshoot a problem encountered by a particular type of service or product model. For example, use a speed test to troubleshoot the internet-related issues.
* **[Define a characteristic for the test definition](https://servicenow-prod.fluidtopics.net/0eVoiQGqhtkNT_RBai8laQ)**   
  Add a characteristic for a test to determine the properties that are required to run and evaluate the test.
* **[Define the relationship between the test definitions](https://servicenow-prod.fluidtopics.net/Ek_mZzozjWGZCyWYPP3kOA)**   
  Define relationships for a test definition to connect and associate it with other test specifications. This process ensures comprehensive testing coverage and that the tests are aligned with the testing goals.
* **[Define test definition relationships with specifications](https://servicenow-prod.fluidtopics.net/wyFo6nss7A6UkQql7vjwUg)**   
  Establish a relationship between test definitions and their respective specifications or product model to determine the tests that must be executed for a given inventory. This relationship ensures that the appropriate tests are identified and executed based on the defined specifications. Without this association, the system can't accurately assign the necessary tests for each inventory item.
* **[Define test measure definitions for a service test](https://servicenow-prod.fluidtopics.net/JA2BbH~WHF~UKxowQEXO8w)**   
  Define unique test metrics, such as parameters and criteria to run the test on a given service during testing. These metrics help promote that the service meets the desired standards and requirements to provide a satisfactory user experience.
* **[Define threshold rules for a test measure definition](https://servicenow-prod.fluidtopics.net/cHq2cZZSbFXdqhzsDL0x4g)**   
  Set rules or criteria to evaluate the results of test measures. These rules establish thresholds that determine the acceptable performance and quality metrics for a service under evaluation. If test measure results exceed or fall below these thresholds, it indicates a deviation from expected performance levels.
* **[Define measure consequences for the threshold rules](https://servicenow-prod.fluidtopics.net/YIUpEbc_2Jn3K126BBtl~w)**   
  Set actions or responses to trigger when the test measure results fall outside the predefined acceptable limits.
* **[Publish test definitions](https://servicenow-prod.fluidtopics.net/Sy_ykJslOdfVi6rXTpnE8Q)**   
  Publish the test definitions to ensure that agents only see the approved versions of test definitions for execution. This also helps maintain consistency and control over both current and future test versions.