Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions skills/uipath-test/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -51,19 +51,19 @@

Projects: `uip tm project list --filter <NAME_OR_KEY>`; `project create --name <PROJECT_NAME> --project-key <PROJECT_KEY>`; `project update --project-key <PROJECT_KEY> --name <PROJECT_NAME>` (name/description); `project delete --project-key <PROJECT_KEY>`; `project set-default-folder --project-key <PROJECT_KEY> --folder-key <FOLDER_KEY>`; `project clear-default-folder --project-key <PROJECT_KEY>`; `project owners list --project-key <PROJECT_KEY> [<PROJECT_KEY> ...]`. Folders: `uip or folders list -n <name> --all --output json` returns all visible folders.

`project list`, `create`, and `update` rows carry `IsDefault`. Inspect with `uip tm project list --limit 1 --output json` without `--filter`; first row is default only when `Data[0].IsDefault` is `true`, otherwise report "no default visible", not as "the tenant has none" (it may have none, or this login may lack access). `uip tm project get-default --output json` returns or creates `Default Project`, key `TMDP`, opened to the tenant's Everyone group; run only when work needs a project, never merely to inspect. <!-- Intended: get-default may create the tenant's default without asking; the agent then says which project it used. --> When the user asks to create test cases, test sets or requirements, or to run a package, and names no project, run `get-default`, use its `ProjectKey`, and tell the user the work went into that project (name and key). Only for new work: to read, change or delete existing items, ask for the project (Quick Start step 2). `uip tm project update --project-key <PROJECT_KEY> --set-default --output json` makes an existing project default (needs `TM.Administration` or tenant administrator); access does not change, so inaccessible projects yield `permission_denied` from `get-default`. There is no `project create --set-default`. For `permission_denied` from either command report `Message` and `Instructions` and stop (Rule 10).
`project list`, `create`, and `update` rows carry `IsDefault`. Inspect with `uip tm project list --limit 1 --output json` without `--filter`; first row is default only when `Data[0].IsDefault` is `true`, otherwise report "no default visible", not as "the tenant has none" (it may have none, or this login may lack access). `uip tm project get-default --output json` returns or creates `Default Project`, key `TMDP`, opened to the tenant's Everyone group; run only when work needs a project, never merely to inspect. <!-- Intended: get-default may create the tenant's default without asking; the agent then says which project it used. --> When the user asks to create test cases, test sets or requirements and names no project, run `get-default`, use its `ProjectKey`, and tell the user the work went into that project (name and key). To run a package with no project named, leave out `--project-key` (see Run an uploaded package). Only for new work: to read, change or delete existing items, ask for the project (Quick Start step 2). `uip tm project update --project-key <PROJECT_KEY> --set-default --output json` makes an existing project default (needs `TM.Administration` or tenant administrator); access does not change, so inaccessible projects yield `permission_denied` from `get-default`. There is no `project create --set-default`. For `permission_denied` from either command report `Message` and `Instructions` and stop (Rule 10).

`uip tm project-permissions get` returns `Data.Permissions` (the permission names the **caller** holds on that project) and `Data.Count`; it requires `Project.Read`, so success includes `Project.Read` (`Count >= 1`). No access is 403 (or 404 for unseen project), never successful empty permissions. Only `get` is exposed. `uip tm project settings get --project-key <PROJECT_KEY>` reads time zone, execution-name format, step cap, default folder, and governance; `project settings update --project-key <PROJECT_KEY> [--time-zone <IANA_NAME>] [--execution-name-format <TEMPLATE>]` writes only the first two. IANA names, placeholders, read-only fields and half-applied updates: [references/project-settings-guide.md](references/project-settings-guide.md).

Requirements: `uip tm requirements list --project-key <PROJECT_KEY>` optionally `--test-case-id <UUID>` (requirements a test case covers — use this, never scan `list-testcase-ids` per requirement), `--filter`, `--labels`, `--requirement-ids`, `--limit`, `--offset`. Also `list-by-test-execution --project-key <PROJECT_KEY> --execution-id <uuid>`; `get --project-key <PROJECT_KEY> (--requirement-id <uuid> | --requirement-key <key>)` (mutually exclusive); `create --project-key <PROJECT_KEY> --name <name>`; `update --project-key <PROJECT_KEY> --requirement-id <uuid>` (name/description, at least one); `delete --project-key <PROJECT_KEY> --requirement-ids <uuid...>`; `export --project-key <PROJECT_KEY> --output-file <path>` (`.xlsx`); `list-testcase-ids --project-key <PROJECT_KEY> --requirement-id <uuid>`; `testcases --project-key <PROJECT_KEY> --requirement-id <uuid> (--add-testcase-ids <uuid...> | --remove-testcase-ids <uuid...>)` (mutually exclusive).

Migration: `uip tm project export` → `uip tm project import` moves or backs up a whole project as `.tmh`; see [references/project-migration-guide.md](references/project-migration-guide.md). Jobs: `uip tm migration get|list|download`; schemas: `uip tm migration schemas list|download`. These are minutes-long jobs: pass `--wait` (export also `--output-file`), otherwise use the job id with `migration get`; never start another export/import to check. Automation is included by default (`--exclude automation` drops it); governance, project config (Test Cloud only, otherwise 403), and prompts require `--include`. Test sets travel only as `.tmh`; cases/requirements may also use Excel (`testcases export`, `requirements export`). If export format/purpose is unspecified ask. Before import ask existing versus new project (`--create-project`); for a taken key ask for `--new-project-key`.

Check warning on line 60 in skills/uipath-test/SKILL.md

View workflow job for this annotation

GitHub Actions / skills/uipath-test

Possibly stale `uip tm migration schemas list|download` (valid prefix: `tm migration schemas`)

Check warning on line 60 in skills/uipath-test/SKILL.md

View workflow job for this annotation

GitHub Actions / skills/uipath-test

Possibly stale `uip tm migration get|list|download` (valid prefix: `tm migration`)

### AI on requirements and prompt library

`uip tm requirements generate-testcases`, `uip tm requirements evaluate`, and `uip tm requirements find-obsolete-testcases` start jobs and return `ActivityId`; **each start spends AI units: start once, then reuse `--activity-id <ACTIVITY_ID>` to wait/show/create/unlink/delete; never start again to retry.** Use bounded `--timeout 540` and a 600 s shell limit. Scenarios, `Score`, `ConfidenceLevel`, and outcomes: [references/requirement-ai-guide.md](references/requirement-ai-guide.md).

`uip tm prompts list|get|create` manages reusable project AI guidelines. `ModeOfUse` (`--mode-of-use` on `create`, `--modes-of-use` on `list`) is the Autopilot offering; ask when none is named. There is no `update` or `delete`; names are not unique. Before create run `get --name <NAME>` (exact, case-sensitive); `ErrorCode: not_found` means absent, not Rule 10 stop. If found, do not recreate; report it and say changes require Test Manager UI. Several matches: `get` fails; use `--prompt-id` from `list`. `list` mixes `PromptType: Internal` samples and `UserDefined` team prompts; `--filter` is a prefix match on name or description. Guidelines are required, max 4096 characters, via `--guidelines` or multiline `--guidelines-file`; over-limit fails before sending. AI requirement commands take no prompt id: pass library `Guidelines` as `--instructions`. Export with `uip tm project export --include prompts`; default export omits them.

Check warning on line 66 in skills/uipath-test/SKILL.md

View workflow job for this annotation

GitHub Actions / skills/uipath-test

Possibly stale `uip tm prompts list|get|create` (valid prefix: `tm prompts`)

### Test cases

Expand Down Expand Up @@ -103,15 +103,15 @@

### Test set schedules

Verbs: `uip tm schedules create|update|list|next-runs|enable|disable|delete`; `list` is the only read and has no get by id. Recover values with `list` before `update`; update replaces the whole definition (pass every flag you want kept) and cannot change enabled state (use enable/disable). `delete` and `--all` require `--yes`. `--cron` has 6 or 7 fields starting with seconds, not Unix cron; daily 02:00 is `0 0 2 1/1 * ? *`; five fields are refused client-side. Every recurrence requires `--cron-details` JSON. `--start-time`/`--disable-time` are wall-clock `YYYY-MM-DDTHH:mm` in `--timezone`; seconds and `Z` are refused. Pass `next-runs` ids from `list`; the underlying endpoint uses another GUID and returns `200` with an empty list for a bad id. See [references/schedules-guide.md](references/schedules-guide.md).

Check warning on line 106 in skills/uipath-test/SKILL.md

View workflow job for this annotation

GitHub Actions / skills/uipath-test

Possibly stale `uip tm schedules create|update|list|next-runs|enable|disable|delete` (valid prefix: `tm schedules`)

### Run an uploaded package (CI)

`uip tm run --type package --package-name <PACKAGE_NAME> --package-version <VERSION> --folder-path <FOLDER_PATH> --project-key <PROJECT_KEY> --output json` runs every test in an uploaded Orchestrator package, re-runs failures with `--max-retries <N>`, and writes a report. Pack/upload first with `uip rpa pack` / `uip or packages upload`. Without a project run `uip tm project get-default --output json` and use `ProjectKey`. Get `<VERSION>` from `uip or packages versions <PACKAGE_NAME> --folder-path <FOLDER_PATH> --output json`; app version `1.0` selects latest `1.0.x`; exact versions must be latest patch, while older versions exit 3 with nothing created. Under a CI limit pass `--timeout <SECONDS>` below it (default 7200); a step killed first leaves no report. Exit 1 with `RunPackageTestsFailed`/`RunPackageCancelled` is a test result: report it (Rule 10(d)). Exit 4 means timeout: execution may continue and `Data.OutputPath` contains a partial report with unfinished tests skipped; report timeout and never count skipped as passed. Other nonzero exits stop (Rule 10). `--input-path` names that no test declares are listed in `Data.IgnoredInputs`; tell the user (usually a typo).
`uip tm run --type package --package-name <PACKAGE_NAME> --package-version <VERSION> --folder-path <FOLDER_PATH> [--project-key <PROJECT_KEY>] --output json` runs every test in an uploaded Orchestrator package, re-runs failures with `--max-retries <N>`, and writes a report. Pack/upload first with `uip rpa pack` / `uip or packages upload`. With no project named, leave out `--project-key`: the command runs in the tenant's default project (creating it if there is none, like `get-default`) and `Data.ProjectKey` names it; tell the user that project. A `permission_denied` about the default project stops (Rule 10). Get `<VERSION>` from `uip or packages versions <PACKAGE_NAME> --folder-path <FOLDER_PATH> --output json`; app version `1.0` selects latest `1.0.x`; exact versions must be latest patch, while older versions exit 3 with nothing created. Under a CI limit pass `--timeout <SECONDS>` below it (default 7200); a step killed first leaves no report. Exit 1 with `RunPackageTestsFailed`/`RunPackageCancelled` is a test result: report it (Rule 10(d)). Exit 4 means timeout: execution may continue and `Data.OutputPath` contains a partial report with unfinished tests skipped; report timeout and never count skipped as passed. Other nonzero exits stop (Rule 10). `--input-path` names that no test declares are listed in `Data.IgnoredInputs`; tell the user (usually a typo).

### Logs, reports, attachments, and results

Start/finish: `uip tm testcaselog start --project-key <PROJECT_KEY> --execution-id <EXECUTION_ID> --test-case-id <TEST_CASE_ID>` optionally `--run-id <NUMBER>`. Finish with `finish --project-key <PROJECT_KEY> --execution-id <EXECUTION_ID> --test-case-id <TEST_CASE_ID> --result <None|Passed|Failed|Restricted> --has-error <true|false> --executed-by <EMAIL>`; all mandatory; omission gives `ValidationError`/exit 3 with empty message. `--executed-by` is validated non-empty then discarded; stored `ExecutedBy` is authenticated caller. If no executor is named, use `uip login status` → `Data.UserEmail`; never say the result was attributed to the named executor. Optional: `--detail-link <URL>`, `--run-id`, `--is-post-condition-met`, `--step-logs <json>`, `--step-logs-file <path>`. `start` needs an existing execution; open one with `uip tm testcases run … --execution-type manual` or `testsets run … --execution-type manual`. <!-- Verified 2026-10-22, CLI 1.205.0 on alpha: finish without --executed-by fails ValidationError/exit 3 even with --has-error. -->

Check warning on line 114 in skills/uipath-test/SKILL.md

View workflow job for this annotation

GitHub Actions / skills/uipath-test

Possibly stale `uip tm testcases run …` (valid prefix: `tm testcases run`)

Record manual step results on finish (`--step-logs`/`--step-logs-file`): `start` returns testcase-log `Id` and creates one step log per step. List with `uip tm teststeplog list --project-key <PROJECT_KEY> --test-case-log-id <TEST_CASE_LOG_ID> --output json`; pass each back as `{"id":"<STEP_LOG_ID>","testCaseLogId":"<TEST_CASE_LOG_ID>","result":"Passed","comment":"<text>","hasError":false}`. Match step-log `id`, not `testStepId`; unknown ids are silently ignored; only `result`, `comment`, `hasError`, and `hasAttachment` persist.

Expand All @@ -137,9 +137,9 @@

`uip tm wait --execution-id <EXECUTION_ID>` waits for terminal state; optionally `--project-key`, `--test-set-key`, `--timeout <SECONDS>`. `uip tm user get` gets the authenticated profile.

Project-scoped custom-field definitions attach to Requirement/TestCase/TestSet, with per-object label/value rows, via `uip tm customfield …`. For full surface, scopes, case-sensitive `--object-type`/`--data-type` enums (`Requirement|TestCase|TestSet`, `Text|Label`), `--values` JSON semantics, and every label/value verb, read [references/custom-fields-guide.md](references/custom-fields-guide.md).

Check warning on line 140 in skills/uipath-test/SKILL.md

View workflow job for this annotation

GitHub Actions / skills/uipath-test

Possibly stale `uip tm customfield …` (valid prefix: `tm customfield`)

Use `uip tm objectlabel …` for metadata on `Requirement`, `TestCase`, `TestSet`, `TestExecution`, or `TestCaseLog`. Read [references/object-labels-guide.md](references/object-labels-guide.md), especially label id versus object id and `--remove-other-labels` deleting hidden internal labels.

Check warning on line 142 in skills/uipath-test/SKILL.md

View workflow job for this annotation

GitHub Actions / skills/uipath-test

Possibly stale `uip tm objectlabel …` (valid prefix: `tm objectlabel`)

### Performance (load) testing

Expand Down
Loading