In this comprehensive guide, I will walk you through exactly how to execute test cases in Azure DevOps. I will cover everything from setting up your initial test plans to running manual tests and even touching upon the workflow for automated execution. My goal is to help you master this environment.
How to Execute Test Cases in Azure DevOps
The Hierarchy of Artifacts
In Azure DevOps, testing artifacts are structured logically to support traceability. Here is how:
- Test Plan: The root container. This usually corresponds to a Sprint (e.g., “Sprint 24 Plan”) or a specific Release (e.g., “Q3 Release Candidate”).
- Test Suite: These are folders within the plan. They can be static (custom grouping), requirement-based (linked to User Stories), or query-based (dynamic lists based on criteria).
- Test Case: The actual script containing steps, expected results, and test data.
Prerequisites: Setting the Stage for Execution
You cannot execute what doesn’t exist. Before clicking “Run,” I always ensure my test repository is pristine. Here is the checklist for my projects:
- Access Levels: Ensure your team members have “Basic + Test Plans” access level or a Visual Studio Enterprise subscription. Basic access alone will not let you execute tests in the Test Plans module.
- Test Plan Creation: I always name my test plans clearly. For example, “Project Phoenix – Sprint 5.”
- Test Case Readiness: All test cases must be in the “Ready” state. I never let my team execute a test case that is still in “Design” because it skews our metrics.
Table: Essential Permissions for Test Execution
| Permission Name | Description | Recommended Role |
| View Test Runs | Allows viewing of historical test results. | Stakeholders / PMs |
| Create Test Runs | Required to actually execute a test case. | QA Engineers / Developers |
| Manage Test Plans | Ability to create and edit plans and suites. | QA Leads / Managers |
| Delete Test Runs | Removes execution history (use with caution). | Admins Only |
Step-by-Step Guide: Executing Manual Test Cases
This is the bread and butter of our daily work. While automation is critical, manual testing remains essential for exploratory checks and UI/UX validation. Here is the exact workflow.
First, log in to your Azure DevOps organization and navigate to your project.
- Click on Test Plans in the left-hand navigation bar.
- Select Test Plans again from the sub-menu.
- Select the specific Test Plan you are working on (e.g., “Sprint 12”).
- Click on the Execute tab. This is where the magic happens. You will see a list of your test points (pairings of test cases and configurations).
2. Launching the Runner
Highlight the test case you want to run. You have two primary options here:
- Run for web application: This launches the web-based runner.
- Run for desktop application: This launches the separate client runner (useful for non-web apps).
For 90% of my web-based projects, I use the Run for web application option.
- Select the test case.
- Click the Run button (or right-click and select Run with options if you need to choose a specific build or configuration). Check out the screenshot below for your reference.
3. The Execution Phase
Once the pop-up window (The Test Runner) opens, the system will dock to the side of your browser. This allows you to see your application on the main screen while having your test steps visible on the side. Check out the screenshot below for your reference.
My Workflow During Execution:
- Step-by-Step Verification: I go through each step carefully. As I complete an action, I click the Green Checkmark next to the step to mark it as passed.
- Recording Evidence: If a step is critical, I use the camera icon with