locked
VSTS Test Cases RRS feed

  • Question

  • Hi all, my QA manager has the below questions and i'm not sure of the answers.

    1. How to save the Test Cases for each Iteration
    2. How to export the Test Cases and in which format they have to be
    3. How to report generic Bugs that are not attached to a Task work item.

    Please Help! Thanks in advance.
    Wednesday, May 27, 2009 1:53 PM

Answers

  • When you say a Test Case, is that the work item type Test Case?

    In that case

    1. A work item can be assigned to an iteration, you can either create other iterations that are generic, or use a parent iteration path to indicate it belongs to the complete life cycle, or update the iteration path on each iteration

    2. You can export a test case to excel

    3. You can create a bug, which is also a work item. You don't have to assign a bug to a task.


    Ewald - Please remember to mark the replies as answers if they help.
    • Marked as answer by Bill.Wang Thursday, June 25, 2009 9:06 AM
    Wednesday, May 27, 2009 2:12 PM
  • 1. There is no 'out of box' workitem type named Test Case but you can create a custom workitem type if you need to. Have a look at http://www.dotnetcurry.com/ShowArticle.aspx?ID=153 for further information on workitem type customization. If you create such a custom workitem then you can associate it with any iteration that you may have defined in the Team Project. If you do not have such a workitem type then you can write Test Case in any document and link or attach that with some other workitem like a Task or Scenario which is further associated with the iteration.
    2. If you create the Test Case workitem type then you can also write a custom tool that uses Team Foundation Object Model (and optionally VSTO) to import / export data from workitem fields in-out of documents.
    3. If you mean how to create a report which will list bugs which are not linked to any Task type of workitem then you will have to create it as custom report using either BI Studio or Report Builder (Part of Report Manager of SQL Server Reporting Service) or ad-hoc report in MS Excel Pivot Table.
    VP, Technology, SEED Infotech Ltd.
    • Marked as answer by Bill.Wang Thursday, June 25, 2009 9:06 AM
    Wednesday, May 27, 2009 4:42 PM
  • My perception of your case now is that testers write test case (steps to execute test with expected output) in some document like MS Word / MS Excel etc. and you would like to know how to automatically execute those steps.
    These kind of test cases can be used only for manual test. Check this documentation for Manual Test - http://msdn.microsoft.com/en-us/library/ms182617.aspx
    Manual Test accepts the test cases written only in Text or Doc (MS Word) format. No further support is provided to import the test cases in VSTS. As in my earlier post, you can link / attach your test case document to task workitem which is created to execute the test.
    VP, Technology, SEED Infotech Ltd.
    • Marked as answer by Bill.Wang Thursday, June 25, 2009 9:06 AM
    Wednesday, May 27, 2009 5:42 PM
  • That what you ask is handled in VSTS 2010. In there you can define test cases with great integration of an manual test runner.
    Ewald - Please remember to mark the replies as answers if they help.
    • Marked as answer by Bill.Wang Thursday, June 25, 2009 9:06 AM
    Wednesday, May 27, 2009 6:50 PM

All replies

  • When you say a Test Case, is that the work item type Test Case?

    In that case

    1. A work item can be assigned to an iteration, you can either create other iterations that are generic, or use a parent iteration path to indicate it belongs to the complete life cycle, or update the iteration path on each iteration

    2. You can export a test case to excel

    3. You can create a bug, which is also a work item. You don't have to assign a bug to a task.


    Ewald - Please remember to mark the replies as answers if they help.
    • Marked as answer by Bill.Wang Thursday, June 25, 2009 9:06 AM
    Wednesday, May 27, 2009 2:12 PM
  • 1. There is no 'out of box' workitem type named Test Case but you can create a custom workitem type if you need to. Have a look at http://www.dotnetcurry.com/ShowArticle.aspx?ID=153 for further information on workitem type customization. If you create such a custom workitem then you can associate it with any iteration that you may have defined in the Team Project. If you do not have such a workitem type then you can write Test Case in any document and link or attach that with some other workitem like a Task or Scenario which is further associated with the iteration.
    2. If you create the Test Case workitem type then you can also write a custom tool that uses Team Foundation Object Model (and optionally VSTO) to import / export data from workitem fields in-out of documents.
    3. If you mean how to create a report which will list bugs which are not linked to any Task type of workitem then you will have to create it as custom report using either BI Studio or Report Builder (Part of Report Manager of SQL Server Reporting Service) or ad-hoc report in MS Excel Pivot Table.
    VP, Technology, SEED Infotech Ltd.
    • Marked as answer by Bill.Wang Thursday, June 25, 2009 9:06 AM
    Wednesday, May 27, 2009 4:42 PM
  • Thanks for the replies guys.

    I'm not talking about Test Case work item. That's not intended.

    Allow me to clarify:
    1. Testers write Test Cases. How to implement the same using VSTS 2008?
    2. Suppose Testers write test cases in some other tool. How to import those test cases into VSTS?

    Wednesday, May 27, 2009 5:14 PM
  • My perception of your case now is that testers write test case (steps to execute test with expected output) in some document like MS Word / MS Excel etc. and you would like to know how to automatically execute those steps.
    These kind of test cases can be used only for manual test. Check this documentation for Manual Test - http://msdn.microsoft.com/en-us/library/ms182617.aspx
    Manual Test accepts the test cases written only in Text or Doc (MS Word) format. No further support is provided to import the test cases in VSTS. As in my earlier post, you can link / attach your test case document to task workitem which is created to execute the test.
    VP, Technology, SEED Infotech Ltd.
    • Marked as answer by Bill.Wang Thursday, June 25, 2009 9:06 AM
    Wednesday, May 27, 2009 5:42 PM
  • That what you ask is handled in VSTS 2010. In there you can define test cases with great integration of an manual test runner.
    Ewald - Please remember to mark the replies as answers if they help.
    • Marked as answer by Bill.Wang Thursday, June 25, 2009 9:06 AM
    Wednesday, May 27, 2009 6:50 PM