"Test Case Migrator Plus" (Excel/MHT) Tool

Overview

Test Case Migrator Plus tool allows test related artifacts, present in Excel and MHT/Word formats, to be imported into Team Foundation Server. It works with both Visual Studio 2010 and Visual Studio 2012.

The tool contains 2 workflows, the Excel based workflow and the MHT/doc workflow, each of which is described below:

Excel based workflow:

• Migrates Test case information (along with Test Steps) present in Excel into Team Foundation Server – This is a ONE way migration only.
• Migrates work items belonging to Requirement/User story and Bug work item types present in Microsoft Excel into Team Foundation Server – This is a ONE way migration only.
• Supports multi-pass migration process - i.e., each work item type has to be migrated in a different invocation/session of the tool.
• Maintains links between work item types (Parent/Child, Related, Tested By, Tests etc) across multiple passes.
• Provides ability to create Test suites for a test case work item type.
• Provides a wizard based UI to run the tool one Excel file in a single run.

MHT/Doc based workflow:

• Migrates Visual Studio 2005/2008 manual test templates present in MHT/doc formats into Team Foundation Server – This also is ONE way migration only.
• Provides a wizard based UI to run the tool iterating over multiple MHT/Doc files within a folder in a single run.

Capabilities common to both Excel and MHT/doc workflows:

• Provides a command line support to run the tool in a batch mode.
• Allows you to save your selections/configurations into a settings/mappings file to be reused later.
• Default settings/mapping file that works across AGILE, CMMI and SCRUM based projects is shipped along with the tool.

These capabilities allow 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 Visual Studio 2010 / Visual Studio 2012 post migration.

Pre-Requisites

For Visual Studio 2010:

Before you can run the “Binaries for VS2010 - Test Case Migrator Plus V1.2 RTM” tool, both the following pre-requisites need to be present on the machine. Without these, the tool will not function.

• Microsoft Visual Studio 2010 RTM/SP1 bits
  • Microsoft Visual Studio 2010 Ultimate Edition RTM (Web Install) (OR)
  • Microsoft Visual Studio 2010 Premium Edition RTM (Web Install) (OR)
  • Microsoft Visual Studio Test Professional RTM (Web Install) AND Microsoft Visual Studio 2010 Team Explorer (ISO) Explorer (ISO)
• Version of Microsoft Office 2003 or beyond

For Visual Studio 2012:
Before you can run the “Binaries for VS2012 - Test Case Migrator Plus V1.2 RTM” tool, both the following pre-requisites need to be present on the machine. Without these, the tool will not function.

• Microsoft Visual Studio 2012 bits
  • Microsoft Visual Studio 2012 Ultimate (Web Install) (OR)
  • Microsoft Visual Studio 2012 Premium (Web Install) (OR)
  • Microsoft Visual Studio 2012 Test Professional (Web Install)
• Version of Microsoft Office 2003 or beyond

Installation

If you have Visual Studio 2010 client bits installed, then:
Download the “Binaries for VS2010 - TestCaseMigratorPlus(Excel-MHT) V1.2 RTM.zip" and extract it to a folder and start the TestCaseMigratorPlus.exe application. Along with the binaries package, the other files that might be useful include the Readme document, the Linking internals document and the samples package (one for Excel & other for MHT). The sample packages contain corresponding setting file that you can use to jump start the migration process.

If you have Visual Studio 2012 client bits installed, then:
Download the “Binaries for VS2012 - TestCaseMigratorPlus(Excel-MHT) V1.2 RTM.zip" and extract it to a folder and start the TestCaseMigratorPlus.exe application. Along with the binaries package, the other files that might be useful include the Readme document, the Linking internals document and the samples package (one for Excel & other for MHT). The sample packages contain corresponding setting file that you can use to jump start the migration process.

If you have both Visual Studio 2010 and Visual Studio 2012 client bits installed on your machine, then either of the above will work.

Note: Both the VS2012 or the VS2010 version of the tool allows you to connect to a hosted Team Foundation Server, Team Foundation Server 2010 or Team Foundation Server 2012.

Usage

Refer to the TestCaseMigratorPlus(Excel-MHT)-Readme document in the downloads section for a step by step description of how to use the "Test Case Migrator Plus" (Excel/MHT) tool - both in UI mode and command line mode. Refer to the LinksMapping(Excel)-Internals-Readme for an in-depth look at how the links are migrated with this tool.

What's new for the V1.2 RTM version

This release (V1.2 RTM) includes:

• Support for connecting to Hosted Team Foundation Server.
• Support for connecting to Team Foundation Server 2012.
• Fix to issue with read-only attribute being set for LinksMapping-ReportFile which may have led to problems when saving the report file.
• Fix to issue with “related links” not being set properly in certain conditions.
• Fixes to ensure that tool works fine when the Excel file contained rich text data.
  • Note: Data is still imported in plain text only.

What's new for the V1.1 RTM version

The V1.1 RTM release includes fixes for 2 reported issues:

Issue#1: The tool crashes when used against a Scrum project template
This version includes the fix that enables you to work with Projects created with the Scrum Template. Without this fix, trying to use the tool against a project created using a Scrum template would either crash the tool or give various errors.
The core problem with the Scrum template was that the “Bug” work item was present in both “Requirements” category and “Bugs” category, whereas the tool was expecting it to be present only in the “Bugs” category. This has now been corrected.

Issue#2: Test Steps/Expected Results imported via tool do not show up in Microsoft Test Runner (MTR) during manual testing
The tool incorrectly imports the Test steps with Expected Results. Any test step with Expected result should be marked as a Validate step, however this was not set appropriately by the tool. As a result, when the test case is executed manually in MTR, the expected result does not show up inline with the test step.
Fix is that the ‘TestStepType’ field for such a test step should be set as TestStepType.ValidateStep
Thanks to kfkyle for submitting this fix

What's new for the RC2 version

With RC2, the following functionality was 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/Iteration 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.