Test Management or Test Management 2.0 ...?

[JanickeE]

I am currently assessing the Test Management plug-in for use in our team. Our needs are simple; we are responsible for multiple applications for a number of customers. Most of our testing is automated, but we need some manual testing before deploying into production. (Not sn apps, btw!) These need to be stored and re-used before the next deploy.

Test Management pros: Easy to arrange tests into sets/suites and assign tests to users.

Test Management cons: One test can only belong to one suite. The test step form is unwieldy and could do with an option to have check-lists instead, (like the test used in Test Management 2.0.) Would be nice to be able to run a single test or a test-set directly from Test/Test Set as well.

Have also had a quick look at Test Management 2.0 as part of this assessment.

Test Management 2.0 pros: Tests are easy to create, a singe test can be run on the fly and the test runner is nifty and elegant.

Test Management 2.0 cons: I have not been able to assign tests and run a test set while assessing TM 2.0 on my dev instance. Can you really only run tests when Test Management 2.0 is installed with Agile og PPM?  There are no videos or anything online that I can find that actually shows TM 2.0 in action. And why do test plans have to be broken down into cycles AND test execution suites with no option to run tests from the test plan?

My question is simply: Will Test Management be supported and developed further in years to come? Or is everything thrown at Test Management 2.0 as of now?

Any thoughts or sharing of experiences with both tools are warmly welcome.

[SusanWinKY]

Jackie,

I have no answers for you but I would like to add some conclusions I have made as a result of the (very quick) analysis I've done of Test Management 2.0 compared to Test Management.

• In 2.0, the Tests are simplistic – there are no detailed description (HTML format), expected results, or actual results.  Some may like the simplicity, but our users are accustomed to Test Management and will miss this additional detail.
• I don’t see a way to associate a Defect to a Test Run.  In Test Management, we have the Report Defect and Assign Defect UI actions on a Test Case.  Creating Defects is something our users are used to doing as part of their testing process.
• I added Tests to a Story using the Sprint Tracking tab of the Agile Board.  When I open a Story, I don’t see the Tests associated to the Story, and I don't see a way to add a Related List that would display them.  Maybe I'm overlooking it?  We do most of our updates from the Story itself, so having this information in a single place is ideal.
• I don’t see where/how to create Test Environments, although the field is available to select on a Test Run. Well, I see the New button when I click the Execution Environment magnifying glass on the Test Run form, but that isn't the ideal user experience.  We'll end up creating a menu for it.

I'm curious if any of this functionality is being considered for the Madrid iteration of Test Management 2.0.

[Luis Franco]

Hi, experts.

Can I add the following comments on these pros and cons:

- Test Management - pros: the link between project tasks and Test Plans which creates a logical link to projects.

- Test Management 2.0 - cons: I couldn't seem to find any link to the project management processes. Is this a wrong analysis on my part or is this really a separate process. It looks like it was made for the agile process only.

Best regards.

[Sylvia10]

Susan, 

Out of curiosity, are you still using Test Management 1.0 or have you moved to Test Management 2.0?

[SusanWinKY]

Hi Sylvia - we are still on 1.0 and plan to stay there until 2.0 has feature parity or ServiceNow deprecates 1.0.