Test Planning Basics – Using Rational Quality Manager to manage agile, waterfall and mobile application testing
Reedy Feggins 120000A43D Visits (12965)
Regardless of whether the project is following a traditional or agile methodology, making quality an integral part of the software lifecycle requires the whole team to collaborate effectively.
IBM Rational Quality Manager (RQM) is a collaborative hub for test planning and managing test results. Built on the Jazz™ platform and part of the Rational solution for Collaborative Application Lifecycle Management, RQM provides organizations with a web-based test management environment that helps test management professionals.
Test plans in Rational Quality Manager (RQM) are customizable live artifacts used to capture the key quality elements, such the test process, strategy, and responsibilities. It also is used to help teams document test schedules, the quality goals, the entry and exit criteria, test suites and test cases,
By using RQM, project (and programs) project teams can customize it to support their needs for test planning, workflow control, tracking and metrics reporting. In addition, each RQM test plan can be linked to the requirements (e.g. Business Needs, Features, Use Cases) and development items (stories, tasks, defects) to enable full traceability.
Each program or project can define their own test plan, or inherit from a master test plan, to help drive quality through all phases of the project lifecycle. The test plans are used to define the objectives and scope for the test effort and contains criteria to help teams determine the answer to this question: "Are we ready to release?"
Test Planning Basics
The test planning often involve the following tasks:
RQM comes with several out of the box test plans for different development processes. By default, Rational Quality Manager includes these predefined user roles. All of which can be extended, modified or deleted to fit the projects needs
In this case, our quality team is following Discipline Agile Delivery approach where we have both concurrent testing and independent testing being performed by the project.
Here are some example test plans
Traditional Test Plan
The default plan provides most if not all the major sections that a traditional quality management plan may require. It of course can be tailored based on the teams needs but provides a good starting point.
Agile Test Plan
Notice how the plan focuses on the key elements required to complete quality planning a specific sprint or iteration. This plan might be used as a child test plan for an internal release or sprint. For smaller teams this might be the only test plan that would be required.
Mobile App Test Plan
As smart phones and portable tablets become the preferred computing platform for millions of people, developers are creating a growing number of mobile applications to either extend existing business servers or to ofter new value added services to this growing user base.
Given the large number of mobile devices and types of mobile apps (native, web, hybrid), there are several obvious aspects that separate mobile apps testing apart from traditional desktop or web testing, such as desktop application tested is on a central processing unit while mobile apps must be tested on handsets from large number of different devices (e.g., Samsung, Nokia, Apple and HTC), each with a different configuration (screen size, memory, connect speed).
Here is a customized test plan in support of Mobile App testing. Notice the sections for test beds, test environments and Normative and Informative Documents (e.g., capture any government regulations or safety guidelines that must be tested)
Making quality an integral part of the software lifecycle requires the whole team to collaborate effectively. In most projects, defects or quality issues often affects software development in a number of key areas:
Avoiding these issues requires test planning that covers every step (or phase) of the software development lifecycle along with effective automation strategies and meaningful metrics that can be used to guide the project better.
To learn more about IBM® Mobile app testing solutions, take advantage of these additional resources: