V1.1 (RTM)

Rating:        Based on 1 rating
Reviewed:  1 review
Downloads: 3369
Change Set: 64239
Released: Jan 2, 2012
Updated: Jan 2, 2012 by ravishan
Dev status: Stable Help Icon

Recommended Download

Application TestCaseMigratorPlus(Excel-MHT) V1.1 RTM Binaries
application, 4585K, uploaded Jan 2, 2012 - 1646 downloads

Other Available Downloads

Source Code TestCaseMigratorPlus(Excel-MHT) V1.1 RTM Source Code
source code, 4674K, uploaded Jan 2, 2012 - 88 downloads
Documentation TestCaseMigratorPlus(Excel-MHT)-Readme
documentation, 2249K, uploaded Jan 2, 2012 - 314 downloads
Documentation LinksMapping(Excel)-Internals-Readme
documentation, 503K, uploaded Jan 2, 2012 - 998 downloads
Example Samples-ExcelPackage-RequirementsBugsTestCases
example, 27K, uploaded Jan 2, 2012 - 209 downloads
Example Samples-MhtPackage-TestCases
example, 12K, uploaded Jan 2, 2012 - 114 downloads

Release Notes

This release (V1.1 RTM) 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

Reviews for this release

     
This tool has been a huge help for us. So far the only problem I encountered was with the mapping. The tool calculates what can be mapped, and will not let you add mappings if it doesn't think you need them. For example, I had a text based "Priority", but it didn't think I needed a mapping for my integer based "Backlog Priority". So I had no way of mapping the text values to numeric values.
by frbaxter on Feb 23, 2012 at 4:07 PM