Study guide
16.3 CI/CD Pipelines with uipcli & Test Manager Traceability
UiPath Automation Developer Professional UiPath-ADPv1
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview & Blueprint Map
1.1 About the UiPath-ADPv1 Exam: Format, Fees & Policies 1.2 The Exam Topics Mapped to This Guide & a Study Plan
2 Chapter 2: REFramework Architecture & State Dynamics
2.1 State Machine Architecture & The Four Core States 2.2 Configuration Management: Settings, Constants, and Assets 2.3 Transaction Types & The Dispatcher vs. Performer Architecture 2.4 Adapting REFramework: Tabular Data, Collections & Linear Processes
3 Chapter 3: REFramework Exception Handling & Recovery
3.1 BusinessRuleException vs. System.Exception Handling Patterns 3.2 Retry Mechanisms: Queue Retries vs. REFramework MaxRetryNumber 3.3 Consecutive System Exceptions & Graceful Process Termination
4 Chapter 4: State Machines, Custom Log Fields & REFramework Testing
4.1 Building State Machine Projects in Studio 4.2 Logging Levels, Robot Logs & Custom Log Fields in REFramework 4.3 Testing a REFramework Project With and Without Orchestrator Queues
5 Chapter 5: LINQ Queries & DataTable Operations
5.1 LINQ Essentials for Collections & Filtering 5.2 Advanced DataTable Querying with LINQ 5.3 In-Memory DataTable Transformations & Column Operations
6 Chapter 6: Regex, DateTime, JSON & Invoke Activities
6.1 Regular Expressions & Text Parsing for Automation 6.2 DateTime Formatting, Timezone Conversions & TimeSpan Calculations 6.3 JSON Parsing, JSONPath & Serialization with Newtonsoft.Json 6.4 Invoke Method & Invoke Code Activities 6.5 Data Referencing in Invokes: DataTable, List & Dictionary Arguments
7 Chapter 7: Modern UI Automation & Unified Targeting
7.1 Modern Design Experience & The Unified Target Concept 7.2 Anchors, Relative Elements & UI Automation Activities 7.3 Dynamic Selectors, Variables & Wildcards in Selectors
8 Chapter 8: Object Repository, Computer Vision & Remote Runtime
8.1 Object Repository & UI Descriptor Libraries 8.2 AI Computer Vision for Unattended & Remote Interfaces 8.3 Automation in Virtual Environments & UiPath Remote Runtime
9 Chapter 9: Advanced UI Automation: Browser Modes, Agentic UI & macOS
9.1 Browser Automation with the WebDriver Protocol 9.2 Agentic UI Automation: ScreenPlay, Semantic Activities & Healing Agent 9.3 macOS Automation: Native Apps, Office Apps & AppleScript
10 Chapter 10: Advanced Control Flow & Exception Architecture
10.1 Flowcharts, Sequences & Parallel Control Flow Patterns 10.2 Global Exception Handler Architecture & ErrorAction Directives 10.3 TryCatch, Retry Scope & Custom Exception Architectures
11 Chapter 11: Orchestrator Queues & Transaction Management
11.1 Queue Architecture, SpecificContent & Transaction Lifecycles 11.2 Queue Items SLA, Postpone, Deadlines & Priority Scheduling 11.3 Bulk Operations, Transaction Status Updates & Queue Triggers
12 Chapter 12: Orchestrator Tenant & Folder Entities
12.1 Asset Types, Per-Robot Assets & External Credential Stores 12.2 Modern Folder Hierarchy, User/Robot Assignment & Permissions 12.3 Storage Buckets, Webhooks & Environment Promotion 12.4 Orchestrator Tags: Labels, Properties & Governance
13 Chapter 13: Unattended Execution, API Triggers & Cloud Robots
13.1 Unattended Job Execution: Folders, Priorities, Background vs. Foreground & Runtimes 13.2 API Triggers: Starting Jobs from External Systems over HTTP 13.3 Serverless and Cloud VM Robots: Cloud-Hosted Execution Options
14 Chapter 14: Monitoring, Recording & Solutions Management
14.1 Orchestrator Monitoring, Trigger Alerts & Job Health 14.2 Job and Transaction Recording: Troubleshooting Faulted Unattended Jobs 14.3 Solutions Management: Packaging and Deploying Automations with Their Resources
15 Chapter 15: Debugging, Remote Debugging & Profiling
15.1 Studio Debugging Tools: Breakpoints, Panels & Execution Control 15.2 Remote Debugging: Remote Machine and Unattended Robot Connections 15.3 Profile Execution: Finding Performance Bottlenecks in Studio
16 Chapter 16: RPA Testing & Test Suite
16.1 UiPath Test Suite Overview, Test Cases & Given-When-Then Structure 16.2 Data-Driven Testing, Test Verification Activities & Mock Activities 16.3 CI/CD Pipelines with uipcli & Test Manager Traceability
17 Chapter 17: Long-Running Workflows, Action Center & Apps
17.1 Long-Running Workflows: Persistence, Suspend and Resume 17.2 Action Center & Human-in-the-Loop Orchestration 17.3 UiPath Apps: Action Apps, Automations & Integration Service
18 Chapter 18: Trigger-Based Attended Automation & Callouts
18.1 Trigger-Based Attended Automation: Forms, Triggers & Global Variables 18.2 Running Local Triggers & the Event Inspection Tool 18.3 Callouts & Forms for Attended Guidance
19 Chapter 19: UiPath Assistant & Robot Sessions
19.1 UiPath Assistant: Automations, Reminders, Widgets & Configuration 19.2 Robot Session (Picture in Picture): Child Session vs. Virtual Desktop
20 Chapter 20: Autopilot for Developers & Autopilot for Everyone
20.1 Autopilot for Developers: AI Assistance in Studio and Studio Web 20.2 Autopilot for Everyone: Chat, Automations & Clipboard AI
21 Chapter 21: API Automation & Integration Service
21.1 Integration Service: Connectors, Connections & Connector Activities 21.2 API Workflows in Studio Web 21.3 HTTP Requests: Web APIs, the Orchestrator API & Connector Requests 21.4 Connector Builder: Custom Integration Service Connectors 21.5 Integration Service Event Triggers: Connected and Disconnected 21.6 GenAI Activities: Generative AI Inside Workflows
22 Chapter 22: Data Service, Context Grounding & Coded Workflows
22.1 Data Fabric (Data Service) Entities: Modeling Business Data 22.2 Data Fabric Activities and the Platform Connector 22.3 Context Grounding: Retrieval-Augmented Generation with Company Data 22.4 Coded Automations: Structure, Arguments & Invoking Workflows 22.5 Coded Automation Services: Orchestrator, UI Automation, Microsoft 365 & Custom Services
23 Chapter 23: Integrated Scenario Practice
23.1 Integrated Scenario Practice: Designing an End-to-End Solution
16.3 CI/CD Pipelines with uipcli & Test Manager Traceability
Key Takeaways Explain This Topic AI
The UiPath CLI (legacy uipcli) analyzes, packs, deploys, and tests automation packages in CI/CD pipelines; a newer uip CLI is also available.
uipcli package analyze checks Workflow Analyzer rules and fails the job with --stopOnRuleViolation; --treatWarningsAsErrors turns warnings into errors.
uipcli package pack runs validation and analysis by default and supports --version or --autoVersion; uipcli package deploy publishes to an Orchestrator tenant and folder.
uipcli test run runs test sets or tests packages in Orchestrator and can output JUnit results for the build server.
Test Manager links requirements to test cases, reports requirement coverage, and can create defects in tools such as Jira from failed results.
Last updated: September 2026
16.3 CI/CD Pipelines with uipcli & Test Manager Traceability
Core Concept: In enterprise Robotic Process Automation, transitioning from manual deployments to Continuous Integration and Continuous Deployment (CI/CD) pipelines is essential for maintaining code quality, governance, and rapid release velocity. Using the UiPath Command Line Interface ( uipcli / UiPath.CLI ) , DevOps engineers can automate static code analysis, package compilation, and regression testing headlessly. By pairing CI/CD pipelines with UiPath Test Manager , organizations achieve bidirectional traceability—linking business requirements in Jira or Azure DevOps directly to automated test cases and automatically logging defects when regression suites fail.
Manual RPA release processes—where developers manually click "Publish" in Studio, export NuGet packages, and hand them off to operations teams for Orchestrator upload—introduce severe operational bottlenecks and human error. Unchecked naming convention violations, hardcoded passwords, unhandled exceptions, and untested edge cases slip into production. A robust CI/CD pipeline establishes automated quality gates that reject substandard code before it ever reaches staging or production environments.
1. The Enterprise RPA CI/CD Architecture
A modern enterprise RPA CI/CD pipeline automates the entire progression of code from developer commit to production deployment: +-----------------------------------------------------------------------------+
- | ENTERPRISE RPA CI/CD PIPELINE |
- | |
- | [ Developer Commit ] ---> [ Git Pull Request (GitHub / Azure Repos) ] |
- | │ |
- | ▼ |
- | +---------------------------------------------------------------------+ |
- | | STAGE 1: Static Code Governance (uipcli package analyze) | |
- | | - Execute Workflow Analyzer rules against project.json | |
- | | - Enforce naming conventions, variable scope, secure strings | |
- | | - FAIL build if Error or Warning count exceeds policy threshold | |
- | +---------------------------------------------------------------------+ |
- | │ Build Passed |
- | ▼ |
- | +---------------------------------------------------------------------+ |
- | | STAGE 2: Automated Packaging (uipcli package pack) | |
- | | - Compile workflow project into strongly versioned NuGet (.nupkg) | |
- | | - Inject semantic version (SemVer) based on build counter | |
- | +---------------------------------------------------------------------+ |
- | │ Package Built |
- | ▼ |
- | +---------------------------------------------------------------------+ |
- | | STAGE 3: Automated Test Execution (uipcli test run) | |
- | | - Dispatch Test Set execution to Orchestrator Testing Robots | |
- | | - Execute Unit and Integration BDD Test Cases | |
- | | - Generate JUnit / NUnit XML result artifacts | |
- | +---------------------------------------------------------------------+ |
- | │ Tests Passed |
- | ▼ |
- | +---------------------------------------------------------------------+ |
- | | STAGE 4: Deployment & Governance Synchronization | |
- | | - Deploy package to Orchestrator feeds (uipcli package deploy) | |
- | | - Sync execution metrics & activity coverage to UiPath Test Manager | |
- | | - Report results to Test Manager and the team's ALM tool | |
- | +---------------------------------------------------------------------+ |
- +-----------------------------------------------------------------------------+
- 2. Mastering the UiPath Command Line Interface ( uipcli / UiPath.CLI )
The UiPath CLI ( uipcli.exe on Windows or multi-platform runner packages) is a specialized command-line utility designed to interface headlessly with UiPath projects, packages, Orchestrator instances, and Test Manager.
- Core Commands and Operational Syntax
- 1. Static Code Analysis: uipcli package analyze
Before building a package, the pipeline checks the project against Workflow Analyzer rules. uipcli package analyze <path-to-project.json> \
- -stopOnRuleViolation \
- -treatWarningsAsErrors \
- -governanceFilePath <policy.json> \
- -resultPath <analysis.json>
Project path: the project.json file, or a folder containing several projects.
--stopOnRuleViolation : the job fails when any rule is violated.
--treatWarningsAsErrors : warnings count as errors.
--governanceFilePath : a governance policy file with Workflow Analyzer rules; the task fails if the file is missing.
--ignoredRules and --analyzerTraceLevel control which rules and messages are used.
Project validation always runs as part of analyze.
2. Package Compilation: uipcli package pack
Once code analysis passes, the project is compiled into a deployable NuGet package ( .nupkg ). uipcli package pack <projectPath> \
- -output <outputFolder> \
- -version <semVerVersion> \
- -autoVersion
--output : The directory where the resulting .nupkg artifact is saved.
--version : Explicit Semantic Versioning string (e.g., 2.1.0-build.452 ).
--autoVersion : Auto-generates a package version.
Project validation and Workflow Analyzer run by default during pack ; --skipValidate and --skipAnalyze opt out.
3. Automated Test Execution: uipcli test run
uipcli test run tests a package or runs an existing test set in Orchestrator, using the Orchestrator URL, tenant, folder, and authentication options. Results can be written in JUnit format so the build server can display them.
4. Deployment: uipcli package deploy
Deploys the validated .nupkg package to UiPath Orchestrator. uipcli package deploy <package-or-folder> <orchestratorUrl> <tenant> \
--orchestratorFolder <folder>
The first positions are the package path, the Orchestrator URL, and the tenant (required for Automation Cloud).
--createProcess (default true) creates or updates the process in the folder.
Note
These commands belong to the legacy .NET CLI ( uipcli.exe ), which remains available for existing pipelines. UiPath also offers a newer uip CLI with a command map from the legacy commands.
3. Integrating CI/CD Engines: Azure DevOps, GitHub Actions & Jenkins
Enterprise organizations leverage different CI/CD platforms. UiPath provides dedicated plugins, extensions, and CLI runners for each major platform.
1. Azure DevOps Pipelines
UiPath publishes an Azure DevOps extension whose tasks wrap the CLI, such as installing the CLI, packing, deploying, running tests, and running jobs. A pipeline can also call the CLI directly: steps:
- script: uipcli package analyze "$(Build.SourcesDirectory)\project.json" --stopOnRuleViolation
- script: uipcli package pack "$(Build.SourcesDirectory)\project.json" -o "$(Build.ArtifactStagingDirectory)" --autoVersion
2. Other Build Servers
Jenkins has a UiPath plugin, and GitHub Actions, GitLab, and other tools can run the CLI in a script step. In every case, the build server reads the CLI exit code to pass or fail the stage and can publish JUnit test results.
4. UiPath Test Manager & Enterprise Traceability
While CI/CD engines handle compilation and execution, UiPath Test Manager delivers the governance layer that connects automated technical execution to high-level business objectives. +-----------------------------------------------------------------------------+
- | BIDIRECTIONAL ALM TRACEABILITY |
- | |
- | ALM Platform (Jira / Azure DevOps) |
- | +---------------------------------------------------------------------+ |
- | | User Story / Requirement: US-9042 "Automate Invoice Discount Logic"| |
- | +---------------------------------------------------------------------+ |
- | │ |
- | │ Bidirectional Sync |
- | ▼ |
- | UiPath Test Manager |
- | +---------------------------------------------------------------------+ |
- | | Requirement: REQ-104 "US-9042 Invoice Discounting" | |
- | | Linked Test Cases: | |
- | | - TC_01: Verify Standard 5% Discount (Passed) | |
- | | - TC_02: Verify Tier_A 10% Discount (Passed) | |
- | | - TC_03: Verify Negative Margin Boundary (FAILED) | |
- | +---------------------------------------------------------------------+ |
- | │ |
- | │ Automated Defect Creation |
- | ▼ |
- | ALM Platform (Jira / Azure DevOps) |
- | +---------------------------------------------------------------------+ |
- | | Defect / Bug: BUG-312 "TC_03 Assertion Failure on Negative Margin" | |
- | | - Attached: Screenshot, Robot Logs, Verification Failure Details | |
- | +---------------------------------------------------------------------+ |
- +-----------------------------------------------------------------------------+
- Bidirectional ALM Synchronization
Test Manager features native, out-of-the-box connectors for Atlassian Jira , Microsoft Azure DevOps , and ServiceNow .
When business analysts and product owners define Epics, User Stories, or Requirements in Jira/ADO, they synchronize automatically into Test Manager as Requirements .
RPA developers and QA engineers link automated Studio test cases to these Test Manager requirements.
Automated Defect Logging
When an automated test fails, Test Manager can create a defect in the connected tool, such as Jira, from the failed result.
The defect can carry:
The exact test case name and failed verification activity.
Full robot execution logs, error messages, and stack traces.
Screenshots captured by verification activities.
Direct links back to the Test Manager execution run for auditability.
Activity Coverage vs. Requirement Coverage
Understanding the distinction between technical coverage and business coverage is a critical exam topic: +-----------------------------------------------------------------------------+
- | ACTIVITY COVERAGE VS. REQUIREMENT COVERAGE |
- | |
- | ACTIVITY (CODE) COVERAGE REQUIREMENT COVERAGE |
- | - Technical Metric - Business Governance Metric |
- | - Calculated by Studio/Orchestrator - Calculated by Test Manager |
- | - Measures: % of workflow activities - Measures: % of User Stories |
- | actually executed during test runs covered by passing test cases |
- | - Formula: - Formula: |
- | (Executed Activities / Total) * 100 (Passing Req Tests / Total) * 100 |
- +-----------------------------------------------------------------------------+
Activity Coverage (Technical Metric):
Measures the percentage of activities within an automation project that were executed during a test run.
If a workflow contains 50 activities and a test run executes 40 of them (with 10 activities inside an unreached exception branch), the Activity Coverage is 80% .
Studio shows activity coverage for test runs started from the Test Explorer, pointing to untested branches such as exception paths.
Requirement Coverage (Business Metric):
Measures the percentage of business requirements (User Stories) that have at least one assigned automated test case whose most recent execution status is Passed .
If a project has 10 business user stories in Jira, and 8 of them have linked test cases that passed, the Requirement Coverage is 80% .
A project could have 100% Activity Coverage but 0% Requirement Coverage if the test cases were never linked to the business requirements in Test Manager!
5. Enterprise Regression Testing Strategies
To balance pipeline velocity with comprehensive quality assurance, enterprise RPA teams implement a two-tiered testing strategy:
Pipeline Tier Trigger Event Scope of Tests Execution Time Objective
Pull Request (PR) Quality Gate Developer creates PR into main branch. Static Code Analysis ( uipcli package analyze ) + Fast Unit Tests (Mocked). A few minutes. Prevent broken code, naming violations, and logic regressions from merging.
Nightly / Promotion Regression Scheduled nightly or triggered upon staging deployment. Full Integration & End-to-End System Test Sets on test machines. Longer runs, often an hour or more. Validate end-to-end multi-application health, system SLAs, and third-party integrations.