Set it up
1
Create an API key
Go to Organization Settings → API Keys, create a key, and copy it when
it is shown. It is not displayed again. Project-scoped keys are bound to one
project. Organization-scoped keys need
projectShortId on API calls.2
Store the token in Azure Pipelines
Add
QATECH_API_TOKEN as a secret pipeline variable. Secret variables
are not exposed to scripts on their own. The step below maps the token
through env.3
Get the short IDs
Copy
proj_… from the project URL or Settings, and pln_… from the test
plan URL. See Find the IDs you
need.What works on Azure DevOps
Run a test plan
ubuntu-latest includes curl and jq. trigger is API: the Start Run API has no Azure DevOps trigger. branch, commitHash, and repository still attribute the run in the dashboard.
pln_abc123 and proj_abc123. A project-scoped key can omit projectShortId.
To test a preview or staging URL for this run, add applications as on API regression testing. Pass DEPLOY_URL between steps the same way as a pull request review.
What this does not do
- This path does not post a pull request review. Use Azure DevOps pull request testing for that.
- The example starts the plan and finishes. To fail the pipeline on the result, follow Blocking.
- Header, basic auth, device preset, and notification overrides are on the Start Run API.