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.

[JanickeE]

Hi Susan. Sorry about the late reply. For the project in question at the time of posting we went with a lightweight cloud-based tool, so no ServiceNow TM or TM 2.0. Mostly it ended up being a question of ease and flexibility, look and feel. Keep in mind that the majority of the systems we are currently testing are NOT ServiceNow apps, so Test Manager was mostly considered because we happened to have a ServiceNow instance and we were assessing these types of tools anyway.

We have a couple of larger ServiceNow projects in the pipeline where we are committed to use the platform all the way through, including the testing (automated and manual). It will be interesting to see if this changes how I experience the ServiceNow test tools.

[gary_hopson]

We are currently looking at Replacing HP ALM with ServiceNow I would be very interested in your selection and if you find it to be a viable solution.

Thanks,

Gary Hopson

Senior IT Quality Analyst

ITG Brands Inc. 

[Luis Franco]

Hi, Gary.

We have moved from HP Alm to Test Management and the biggest requirements for the project:

- Creation of import sets to support the automatic import from an excel

- Adding the html_description field to defect form, to support the copy & paste of print screens directly there on the creation of the defect.

- Creation of M2M tables to support the relationship from requirements and stories (this was a recent request due to initiating the agile process in development teams).

- State model of the defects -> but on this I would recommend to stick to the OOTB because the HP state model is too cumbersome.

Regarding the Test Management 2.0 we are not yet considering because it's lacking the link between project tasks and Test Plan which we appreciate a lot in the Test Management plugin.

Hope this is helpful for your analysis.

Best