aurelienclere-365/ado-cowork-plugin/ado-test-plans

ADO Test Plans

Manage Azure DevOps test plans, test suites, and test cases. Read test execution results from pipeline builds and create structured test artefacts.

When to use

• User wants to see test results for a build or pipeline run
• User wants to create a new test plan or test suite
• User wants to create or update test cases
• User wants to know the pass/fail rate for a release or sprint
• User is preparing a release sign-off and needs test coverage evidence

MCP tools used

Workflow

Getting test results for a build

1. Identify: build ID (if known) or pipeline name + branch.
2. If only pipeline name is known, use ado-pipelines skill to get the build ID first.
3. Call testplan_show_test_results_from_build_id(buildId) — returns pass/fail/skipped

counts per test suite, and the list of failed test cases with error messages.

1. Present the Test Results Summary table.
2. List failing tests in the Failing Tests table.

Listing test plans

1. Call testplan(project) — returns all test plans with ID, name, state, iteration,

and suite count.

1. Present the Test Plan List table.

Creating a test plan

1. Extract: project, plan name, and iteration path.
2. Call testplan_test_plan_write(project, name, iteration).
3. Confirm with the new plan ID.

Creating a test suite

1. Identify the parent test plan ID.
2. Extract: suite name, suite type (static, requirement-based, query-based).
3. Call testplan_test_suite_write(planId, suiteName, suiteType).
4. Confirm with the new suite ID.

Creating a test case

1. Identify the test suite or plan to add the test case to.
2. Extract: test case title, steps (action + expected result pairs), and any associated

work item ID.

1. Call testplan_test_case_write(suiteId, title, steps).
2. Confirm with the new test case ID.

Output Format

Test Results Summary

Build #512 — release-2.0 pipeline

Failing Tests

Test Plan List

Notes

• Test results are associated with a build via the build definition ID and build number.

If the user gives a pipeline name instead of a build ID, resolve it via ado-pipelines skill first.

• When creating test steps, each step has an Action (what the tester does) and an

Expected Result (what should happen). Prompt the user for both if not provided.

• testplan_test_case_write creates a work item of type Test Case in addition to adding

it to the suite — both happen in one call.

Active context

This skill respects the session context set by the ado-context skill.

• If activeProject is set, use it automatically as the project parameter — do not

ask the user to re-specify it.

• If no context is set and a project is required, invoke Workflow E of ado-context

to resolve it (list projects, ask user to pick, then proceed).