Test Execution: Run and Manage Test Run Packs
Open Test Execution to create, run, schedule, and monitor Test Run Packs. Covers the packs table, Run Now, enable/disable scheduling, and viewing run results.
Execution documentation for Shift-Left API: 11 guides, including Test Execution: Run and Manage Test Run Packs; Test Run Pack Wizard: Create a Pack; Manage and Run Execution Packs. Browse the articles below, or use search to jump to a specific task.
11 articles.
Open Test Execution to create, run, schedule, and monitor Test Run Packs. Covers the packs table, Run Now, enable/disable scheduling, and viewing run results.
Build a Test Run Pack in five steps — pack details, test selection, execution preferences, notifications, and scheduling — with the validation rules for each.
After creating a pack, run it now, edit configuration, monitor status, and manage lifecycle actions from the Execution list.
When a run of 200 tests ends with 47 failures, the hard part is not fixing them. It is working out how many different problems those 47 failures actually are.
A green run is good news, but it does not always mean what it seems to. A test that only checks "the status was 200" stays green even if the endpoint starts returning an empty body.
Run a Shift-Left API test pack in a GitHub Actions workflow with the first-party action, gate the build on its pass rate, and publish the JUnit results.
Install the Shift-Left API extension from the Visual Studio Marketplace, add the task to an Azure Pipelines YAML file, gate the build on the pass rate, and publish the JUnit results.
Install the Shift-Left API Jenkins plugin from its .hpi file, add the Run Test Pack build step to a Freestyle job, gate the build on the pass rate, and publish the JUnit results.
Run a Shift-Left API test pack from GitLab CI, CircleCI, Bitbucket Pipelines, TeamCity or any CI that can run curl: sign in, start the pack, wait for the new run, and fail the job below your pass rate.
One answer per API or project, ready, ready with risks, not ready or no evidence yet, with every reason linked to the evidence behind it.
The Quality Agent reviews a whole project on a schedule or on request, puts what it finds in order, and says what to do about each item. It reports. It never runs, rewrites or deletes your tests.