studio
2024.10
true
- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- Control Flow
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- Logging
- The Diagnostic Tool
- Workflow Analyzer
- About Workflow Analyzer
- ST-NMG-001 - Variables Naming Convention
- ST-NMG-002 - Arguments Naming Convention
- ST-NMG-004 - Display Name Duplication
- ST-NMG-005 - Variable Overrides Variable
- ST-NMG-006 - Variable Overrides Argument
- ST-NMG-008 - Variable Length Exceeded
- ST-NMG-009 - Prefix Datatable Variables
- ST-NMG-011 - Prefix Datatable Arguments
- ST-NMG-012 - Argument Default Values
- ST-NMG-016 - Argument Length Exceeded
- ST-NMG-017 - Class name matches default namespace
- ST-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DPB-010 - Multiple instances of [Workflow] or [Test Case]
- ST-DBP-020 - Undefined Output Properties
- ST-DBP-021 - Hardcoded Timeout
- 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
- Arguments
- Imported Namespaces
- Coded automations
- Introduction
- Registering custom services
- Before and After contexts
- Generating code
- Generating coded test case from manual test cases
- Trigger-based Attended Automation
- Recording
- UI Elements
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Citrix Technologies Automation
- RDP Automation
- VMware Horizon Automation
- Salesforce Automation
- SAP Automation
- macOS UI Automation
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Extensions
- About extensions
- SetupExtensions tool
- UiPathRemoteRuntime.exe is not running in the remote session
- UiPath Remote Runtime blocks Citrix session from being closed
- UiPath Remote Runtime causes memory leak
- UiPath.UIAutomation.Activities package and UiPath Remote Runtime versions mismatch
- The required UiPath extension is not installed on the remote machine
- Screen resolution settings
- Group Policies
- Cannot communicate with the browser
- Chrome extension is removed automatically
- The extension may have been corrupted
- Check if the extension for Chrome is installed and enabled
- Check if ChromeNativeMessaging.exe is running
- Check if ComSpec variable is defined correctly
- Enable access to file URLs and Incognito mode
- Multiple browser profiles
- Group Policy conflict
- Known issues specific to MV3 extensions
- List of extensions for Chrome
- Chrome Extension on Mac
- Group Policies
- Cannot communicate with the browser
- Edge extension is removed automatically
- The extension may have been corrupted
- Check if the Extension for Microsoft Edge is installed and enabled
- Check if ChromeNativeMessaging.exe is running
- Check if ComSpec variable is defined correctly
- Enable access to file URLs and InPrivate mode
- Multiple browser profiles
- Group Policy conflict
- Known issues specific to MV3 extensions
- List of extensions for Edge
- Extension for Safari
- Extension for VMware Horizon
- Extension for Amazon WorkSpaces
- SAP Solution Manager plugin
- Excel Add-in
- Test Suite - Studio
- Introduction
- Application Testing
- About the testCases.json file
- Execution Templates
- Mock Testing
- API Test Automation
- Troubleshooting
About the testCases.json file
Studio User Guide
Last updated Nov 18, 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"
}
]
}