Test Management with Azure DevOps+VS

Why Azure DevOps for Test Management?

Azure DevOps integrates work item tracking, test case management, automation execution, and reporting in a single environment. That means requirements, code, and test results live together, reducing the risk of gaps or outdated information.

For QA leaders, this integration offers three major advantages:

• Unified view of progress: See backlog, test design, execution, and results in one place.
• Traceability: Link test cases to user stories, defects, and builds for better root cause analysis.
• Collaboration: Developers, testers, and product owners work from the same data source.

In this example, we use Visual Studio 2019 alongside Azure DevOps, but the principles apply to other versions with similar functionality.

Step 1: Create Backlog Items

In Agile, testing starts with well-defined backlog items. In Azure DevOps, these represent the work the team plans to deliver.

Screenshot Reference: Azure DevOps web access showing “+ New Work Item” button for backlog creation.

From the backlog view, you can add new items via the + New Work Item button. Each item should have a clear title and description so QA can understand what will need to be tested later.

Step 2: Assign Items to Team Members

Once created, backlog items must be assigned to the right person for completion. Assignments ensure that ownership is clear for both development and testing.

Screenshot Reference: Board view in Azure DevOps with an item in “To Do” status, selected to assign a user.

In Agile, these assignments might shift during sprint planning or daily stand-ups, but the board should always reflect the current status so QA knows what’s in progress and when testing can begin.

Step 3: Design Test Cases

Test case design can happen in either Azure DevOps or Visual Studio, but in practice, Azure DevOps is better suited for writing detailed test steps.

In Azure DevOps

From the Boards view, right-click on a backlog item and choose Add Test. Then enter the steps, expected results, and any relevant notes.

Screenshot Reference: Azure DevOps “Add Test” interface linked to a work item.

In Visual Studio

You can link a test case to a work item, but Visual Studio does not support adding step-by-step instructions directly. For detailed test definitions, switch to the Azure DevOps web portal.

Screenshot Reference: Visual Studio Team Explorer showing connection to Azure DevOps project and “New Work Item” creation.

Step 4: Associate Automation Scripts

Linking automated test scripts to test cases allows you to run them directly from Azure DevOps and track results alongside manual tests.

Supported options include languages like C#, Java, and Python, and tools such as Selenium or Coded UI.

Screenshot Reference: Visual Studio solution with an automated Selenium script linked to a test case in Azure DevOps.

Automation linkage can be created in either Visual Studio or Azure DevOps. The key is to ensure the scripts remain in sync with evolving requirements and are updated as part of regular sprint work.

Step 5: Create a Test Plan

A test plan organizes the test cases to be executed in a given cycle — for example, a sprint or release candidate.

Screenshot Reference: Azure DevOps “Test Plans” tab showing a plan named “The third test” with two test cases added.

Plans can be created from scratch or generated automatically when adding tests from backlog items. Structuring your plans by feature, risk level, or release helps prioritize testing and reporting.

Step 6: Execute Test Cases

Execution happens within the Test Plans tab in Azure DevOps.

• Manual tests are run step-by-step, marking each as passed or failed.
• Automated tests can be executed via Run with Options, selecting the build and environment.

Screenshot Reference: Azure DevOps execution screen showing selection of cases and “Run with options” dialog.

This is where tight CI/CD integration pays off — test runs can trigger automatically after a build completes, accelerating feedback loops.

Step 7: Review Results

After execution, results are visible in charts and detailed run reports.

Screenshot Reference: Azure DevOps test run results chart showing pass/fail distribution.

QA leads can review:

• Individual test outcomes.
• Trends over time (e.g., pass rate by build).
• Defects linked to failed tests.

Analyzing these results within the same environment where backlog and development work are tracked makes it easier to spot recurring issues and refine the process.

Making It Work in Agile

While the above steps describe the mechanics, the real value comes from aligning tool use with Agile principles:

• Involve QA early: Link test cases to backlog items during refinement, not after development finishes.
• Keep tests current: Update cases and automation scripts as requirements change.
• Integrate into ceremonies: Use results from Azure DevOps to inform sprint reviews and retrospectives.
• Automate where it saves time: Focus on repetitive or high-value test areas rather than trying to automate everything.

When used this way, Azure DevOps and Visual Studio aren’t just record-keeping tools — they become an active driver of faster, higher-quality delivery.