Studio
2024.10
false
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- The Diagnostic Tool
- Workflow Analyzer
- ST-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DBP-020 - Undefined Output Properties
- ST-DBP-023 - Empty Workflow
- ST-DBP-024 - Persistence Activity Check
- ST-DBP-025 - Variables Serialization Prerequisite
- ST-DBP-026 - Delay Activity Usage
- ST-DBP-027 - Persistence Best Practice
- ST-DBP-028 - Arguments Serialization Prerequisite
- ST-USG-005 - Hardcoded Activity Arguments
- ST-USG-009 - Unused Variables
- ST-USG-010 - Unused Dependencies
- ST-USG-014 - Package Restrictions
- ST-USG-020 - Minimum Log Messages
- ST-USG-024 - Unused Saved for Later
- ST-USG-025 - Saved Value Misuse
- ST-USG-026 - Activity Restrictions
- ST-USG-027 - Required Packages
- ST-USG-028 - Restrict Invoke File Templates
- ST-USG-032 - Required Tags
- ST-USG-034 - Automation Hub URL
- Variables
- Imported Namespaces
- Coded automations
- Trigger-based Attended Automation
- UI Elements
- Selectors
- Object Repository
- Image and Text Automation
- Automating Citrix Technologies
- RDP Automation
- Salesforce Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The WebDriver Protocol
- Test Suite - Studio
- Extensions
- SetupExtensions tool
- Extension for Citrix
- Extension for Microsoft Remote Desktop and Apps
- Excel Add-in
- Troubleshooting
About the testCases.json file
![](https://docs.uipath.com/_next/static/media/grid.05ebd128.png?w=3840&q=100)
Studio User Guide
Last updated Jun 28, 2024
About the testCases.json file
testCases.json
is a file automatically generated when packaging as a
NUPKG a project of type Process, that contains test cases. The file contains
metadata regarding your RPA testing project.
In the NUPKG file of the project, you can find the
testCases.json
file
in the .tmh
directory.
The parameters contained in the
testCases.json
file are described in the
following table:
Parameter | Description |
---|---|
PackageName | Name of the package. |
PackageVersion | Version of the package. |
ProjectId | Unique identifier of the project. |
RpaPackageName | Name of the RPA package created. |
RpaPackageVersion | Version of the RPA package. |
TestCases | Array that lists the test cases for the given process. For each test
case, the following information is included:
|
Type | Type of project, which is always Process. |
Workflows | Array that lists the workflows related to the test cases, including the ID for the entry point, the name, and the type of workflow. |
The following is an example of the contents of a
testCases.json
file
included in a project packaged from Studio.
{
"PackageName": "Testsuite_Tests",
"PackageVersion": "1.0.162152358",
"ProjectId": "<projectid>",
"RpaPackageName": "Testsuite",
"RpaPackageVersion": "1.0.162145743",
"TestCases": [
{
"AutomationId": "<id>",
"RpaPackageEntryPoints": [
{
"Id": "<id>",
"WorkflowName": "Main.xaml"
}
],
"RpaWorkflows": [
],
"TestCaseName": "TestCase.xaml"
}
],
"Type": "Process",
"Workflows": [
{
"EntryPointId": "<entrypointid>",
"Name": "Main.xaml",
"Type": "EntryPoint"
}
]
}
{
"PackageName": "Testsuite_Tests",
"PackageVersion": "1.0.162152358",
"ProjectId": "<projectid>",
"RpaPackageName": "Testsuite",
"RpaPackageVersion": "1.0.162145743",
"TestCases": [
{
"AutomationId": "<id>",
"RpaPackageEntryPoints": [
{
"Id": "<id>",
"WorkflowName": "Main.xaml"
}
],
"RpaWorkflows": [
],
"TestCaseName": "TestCase.xaml"
}
],
"Type": "Process",
"Workflows": [
{
"EntryPointId": "<entrypointid>",
"Name": "Main.xaml",
"Type": "EntryPoint"
}
]
}