There is now a new generation of test management and manual
test assist technologies available from IBM Rational called Rational Quality
Manager (RQM). This web server based
tool is based on the Jazz collaboration platform and has many enhancements and
advanced capabilities not present in the Test Manager and Manual Tester
One of the advantages of Quality Manager is the zero client
install footprint on the tester’s test machine environment. Since RQM is browser based, you don’t have
any test software product to install on all your test machines. This permits you to wipe out and reimage the
test machine and only install the software being tested. A second great advantage is its ability to
support testers in geographically distributed locations from a central server
and provide real time status reports of how that testing is progressing. The third important benefit is the ability to
collaborate through the tool platform, assigning tasks or defects to whomever
on the team needs to address that particular issue. This includes a personal “To Do” list for
each team member as well as the ability to monitor the whole team’s activities
as they happen.
So now that we have discussed the reasons that you may want
to move forward from the individual productivity enhancements afforded by the
Test Manager and Manual Tester approach to add the team oriented, collaborative
approach of Quality Manager, what do you have to do for the migration of your
manual testing project? Basically the
RQM product comes with two migration tools, one for migrating a Test Manager
project to RQM and one for migrating individual Manual Tester tests to RQM.
There are three steps to the migration for those moving to
- Migrate all of your manual tests from Manual Tester to RQM.
- Customize (if desired) any of the custom fields in Test Manager assets using the XML mapping file so that data comes over into the proper fields for Test Plans and Test Cases.
- Run the Test Manager Migration Wizard on a test machine with all of the Test Manager and Manual Test assets in their proper directories so the linkage is preserved over in RQM.
Obviously going from Windows GUI applications like Rational Test Manager and Manual Tester to a web based interface is a big change from a usage model perspective. The layout of controls, the translucent window, the compact views are all gone in the browser interface. However by adjusting the height of the browser panel or using dual or wide monitor space, you can find geometries that permit the visibility of the application under test as well as the manual test execution view in the browser.
Many of our current customers are undergoing this transition
and most have done so with little trouble during the asset migration
process. The usability of the manual
test execution from within RQM is not quite as convenient but is close to the
capability of the Manual Tester product.
Its great advantage is its seamless integration with the test management
and execution views within RQM as well as the roll-up of testing progress
across all of the testers on the team.
For those customers linking to Requisite Pro based
requirements, the story is just as impressive.
By specifying the Requisite Web server during the Test Manager
migration, you even get the Requisite Pro requirements linked in to the test
cases as was the case with the original project assets. No changes are required on the Requisite Pro
side as long as it is the up-to-date version (7.1.1 or later) of the Requisite
Web server. This server can then be
seamlessly integrated as your requirements server for RQM as well.
For anyone contemplating moving from Rational Test Manager and Rational Manual Tester to RQM, I hope this has been a helpful overview of the movement forward. I have attempted to give a little perspective on the benefits of moving ahead to the new IBM Rational Jazz collaborative platform for teams.