TFS 2010 - MTM 2010 Rename Test Plan to "Custom Name" | Rename TestSuite to "Custom Name" - by Allen.Feinberg

Status : 

  Duplicate<br /><br />
		This item appears to be a duplicate of another existing Connect or internal item.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 611121 Comments
Status Closed Workarounds
Type Suggestion Repros 0
Opened 10/6/2010 1:21:28 PM
Access Restriction Public


I just finished a meeting with my testing director and we went over using MTM and TFS 2010 for all future test case management for 2011 and beyond. We have internal in house tools that have been written over the last 10 years (and we've had a number of 3rd party systems Mecury/Quality Center that we've modified extensively so we're familiar with the domain)

She had the following questions/requirements after seeing MTM in action.

•We have a huge knoweldge base around our testing process (15+ years) and we a very specific taxonomy that we use. In order for us to adopt TFS 2010 we'd need to be able to use our taxonmy and not have to conform to the tools taxonomy. [We bought the tool to help us do our jobs...we didn't buy the tool to make our jobs have to work the way the tool was designed.] So we use the term "Test Library" to denote the library of test cases we are working on for a given release. [The term "Test Plan" is already reserved for the formal agreement document we have between Test, Development, QA, and the business]. Can we rename Test Plan in MTM to "Test Library"? 

•We use the term "Test Cycle" to denote the specific tests that we will be executing/running for a planned release phase. This seems to align with the term "Test Suite" in TFS 2010, however we already use the term "test suite" to denote the physical testing area where we execute our tests on physical hardware. Can we rename Test Suite to "Test Cycle"?
Sign in to post a comment.
Posted by jtay2380 on 3/27/2011 at 8:26 PM
Microsoft also does not use the term "Test Case" correclty. A case would represent one line of input parameters with one line of expected results. The fact that you paramatize a Test case doesn't make sense. A case is the most granular form of a test script. It should be a called a test script. Or Test Condition --

Posted by Microsoft on 10/6/2010 at 2:23 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(