V 1.0 (RC2)

Rating:        Based on 2 ratings
Reviewed:  2 reviews
Downloads: 20841
Released: May 7, 2010
Updated: May 12, 2010 by ravishan
Dev status: Beta Help Icon

Recommended Download

Application TestCaseMigratorPlus(Excel-MHT) V1.0 RC2 Binaries.zip
application, 2957K, uploaded May 12, 2010 - 9799 downloads

Other Available Downloads

Documentation TestCaseMigratorPlus(Excel-MHT)-Readme.doc
documentation, 2249K, uploaded May 12, 2010 - 3188 downloads
Documentation LinksMapping(Excel)-Internals-Readme.doc
documentation, 503K, uploaded May 12, 2010 - 2284 downloads
Example Samples-ExcelPackage-RequirementsBugsTestCases.zip
example, 27K, uploaded May 3, 2010 - 3401 downloads
Example Samples-MhtPackage-TestCases
example, 12K, uploaded May 3, 2010 - 1386 downloads
Application TestCaseMigratorPlus(Excel-MHT) V1.0 RC2 Source Code.zip
application, 4677K, uploaded May 12, 2010 - 783 downloads

Release Notes

Test Case Migrator Plus

With the prior releases of Test Case Migrator (Beta and RC1), it was possible to:
  1. migrate test cases (along with test steps) present in Microsoft Excel to VS2010 TCM server AND
  2. migrate VS 2005/2008 test templates present in MHT/doc formats to VS2010 TCM server.
These capabilities allowed you to reap all the benefits associated with Test Case Management (requirements traceability, test coverage, requirements coverage, test execution, test result analysis etc) present in VS 2010 release post migration.

With the RC2 release of this tool, we are adding to the Excel capabilities the ability to migrate not just the Test case work item, but also Requirements and Bugs work items – hence the change in name of the executable to “TestCaseMigratorPlus.exe”. The mht/doc based workflow remains the same – i.e. it only supports migration of work item type present in the VS2005/2008 manual test templates.

What's new in RC2 version:
With this new drop (RC2), the following functionality has been added to the Excel based workflow:
  • Migrate not just Test case, but also Requirement/User story and Bug work item types.
  • Migrate links (using “Links mapping” dialog (Excel flow)) between different work item types across different invocations/sessions of the tool. Refer to “LinksMapping(Excel)-Internals-Readme.doc” for additional details.
  • Default link types supported include:
    • “Parent/Child” links between Requirement::Requirement
    • “Related” links between Requirement::Requirement
    • “Related” links between Test Case::Test Case
    • “Related” links between Bug::Bug
    • “Related” links between Requirement::Bug
    • “Tested By/Tests” links between Requirement::Test Case
    • “Tested By/Tests” links between Bug::Test Case
  • Create Test plans/test suites as part of migration process for a Test case work item type.
  • Create Area Paths at runtime based on folder hierarchy specified in excel file for all supported work item types.
  • Analyze the migration process across different runs using “Consolidated Excel Pivot reports” (Excel flow) in addition to the session based output excel file.
  • Updated and polished UI for the tool – now this is consistent with VS2010 theme.
  • Improved and early inline error handling.

No changes have been made to the mht/doc based workflow other than UI polish.


List of known issues:
  1. CLI does not work with VS command prompt, it does work with normal command prompt.
  2. Crash occurs when Office 2000 (excel/word/mht) is given as input to the tool.

Reviews for this release

     
I used this tool to migrate hundreds of lines of requirements into TFS from an Excel spreadsheet. It worked like a charm! Saved my days of laborious work. Thanks a lot!
by vishantpatel on Nov 10, 2011 at 7:29 PM
     
I feel it can help me to resolve the problem of data exchange between TFS and Word. And However in the example of your project,I find the "Sample_MHT.mht" of "Samples-MhtPackage-TestCases " had a little problem. Its style was not like the Documentation said,whose “fields” highlighted in “Yellow” and “values” for the fields highlighted in “gray” colors.So I cann't achieve the result of "TestCaseMig
by happyadele on Jun 13, 2011 at 7:28 AM