- Get started
- Best practices
- Capabilities
- Skills
- CLI
- Examples
- Examples overview
- Recipe: build an agent
- Recipe: automate with RPA
- Recipe: enter data into a web app
- Recipe: extract data from a desktop app
- Recipe: refactor and test a workflow
- Recipe: a queue-based process with REFramework
- Recipe: build a Maestro Flow
- Recipe: coded app and API workflow
- Recipe: verify a release with Test Manager
- Recipe: extract data from documents with IXP
- Advanced
- Help
This recipe uses a Test Manager project to trigger a test set execution, monitor its completion, retrieve the execution results, and generate a release readiness report — all through a single agent conversation with no manual intervention.
Prerequisites
- The
uipcommand-line interface (CLI), UiPath skills, and an authenticated session. See Install and set up. - A Test Manager project with at least one test set ready to run.
Run the check
-
Open your coding agent in any working folder.
-
Ask it to trigger your test set:
"The hotfix for the order module has just been deployed to production. Trigger the smoke test set from the [project name] project in Test Manager and tell me if everything passed."
Include the project name in your prompt. Without it, the agent searches across all projects to find the test set.
-
Ask the agent for the report once the run is complete:
"Generate a release manager report from Test Manager for test set [name] — I need a go/no-go summary before tonight's sign-off meeting."
-
Review the report the agent returns.
You can ask follow-up questions or request adjustments as needed.
Result
A release readiness summary from Test Manager, produced in the terminal without switching tools.
Exact output and report format depend on your test set configuration and the agent you're using. Confirm results against Test Manager before making release decisions.
See also
For the full list of what your coding agent can do with Test Manager — including querying coverage, generating Quality Assurance (QA) and developer reports, and linking automations — see Tests.