This project has moved. For the latest updates, please go here.

Assigning Test Cases to the "backlog"

Mar 20, 2012 at 9:13 PM


In this document you mention that you should "assign a test case to the backlog".

How do you do this?  In the case of a Test Case, what is the "backlog"?  How do you view the test case "backlog"?

I know how to do this with Product Backlog Items and Bugs, but how do you view the Test Case "backlog?"

- Bruce

Mar 21, 2012 at 1:18 PM

Here's what we do: we set the test case to the backlog when it is a regression test case that has yet to be assigned to a test plan. Also, we assign test cases to the backlog for user stories that are put back into the backlog after they have had test cases developed for them. The backlog is typically the TFS iteration path root for the product or the release. For example, given the followign iteration path hierarchy:

  • Root
    • Release 1
      • Sprint 1
      • Sprint 2
      • Sprint 3

The product backlog is when the test case iteration path is set to Root. The release backlog is when the iteration path is set to Release 1. Check the Visual Studio SCRUM Guidance at for more information.


Mar 21, 2012 at 1:57 PM

Thank you.

- Bruce