Skip to main content

How-to Write and Review a Test Case in ADO

For a new epic, feature, or user story, there may be a need to write new test cases or modify existing test cases. The purpose of this guide is to provide hands-on support to the roles involved in writing, updating, or reviewing test cases of a product.

"Test case" refers to the actions required to verify a specific functionality. A test case details the steps, prerequisites and post-conditions necessary to verify the functionality.

Note: This guide is applicable for both manual and automated test cases (workflow for adding automated test cases using automation tools is not described in this guide).

Intended for​

Product managers, product owners, architects, software engineers, hardware engineers, and test engineers.

Activities​

TC-1

Write a new test case​

A team member creates test cases based on acceptance criteria, system demo/sprint demo, user documentation, implementation proposal document, workflow write-up, or impact area analysis information.

Recommended test case design techniques include:

  • Black box testing techniques like equivalence partitioning, boundary value analysis, decision table testing, state transitioning testing, and use-case based testing.
  • White-box testing techniques like statement testing, decision testing, condition-based testing, and unit testing.
  • Experience-based techniques like error guessing and exploratory testing.

Non-functional test cases must be derived from system epics or epics. If it's missing, then it must be followed up with the product manager or product owner. Else, test cases can be written based on existing knowledge of the product.

NewTC1

NewTC2

Update an existing test case​

In some cases, an existing test case requires an update due to functionality changes. Use the following workflow in such conditions:

  • Create a copy of the existing test case (to enable maintenance of test cases for different versions of the product).
  • Change the test case state from "Ready" to "Design".
  • Update the test case as per the new epic, feature, or user story.

UpdateTC1

updateTC2

Review a test case​

Reviewing test cases helps to ensure that the test cases are correct and that they accurately reflect the requirements and specifications of the software application. New and updated test cases shall be reviewed by the product manager, product owners, architects, developers, and other technical experts.

  • Create a task for review of the test case and link it with the new test case.
  • Add reviewers to the discussion and call to a review meeting for concluding review comments.
  • When the review is completed, send a final review task to the approver.
  • The approver shall set the test case state to "Ready" before the review task is closed.

ReviewTC

References​

Owner: Test Team