The role of three groups in test planning and policy development

The role of three groups in test planning and policy development

Recall that in theTMMframework three groups were identified as critical players in the testing process. They all work together toward the evolution of a quality testing process. These groups were managers, developers/ testers, and users/clients. In TMM terminology they are called the three critical views (CV). Each group views the testing process from a different perspective that is related to their particular goals, needs, and requirements. The manager‘s view involves commitment and support for those activities and tasks related to improving testing process quality. The developer/tester‘s view encompasses the technical activities and tasks that when applied, constitute best testing practices. The user/client view is defined as a cooperating or supporting view. The developers/testers work with client/user groups on quality-related activities and tasks that concern user-oriented needs. The focus is on soliciting client/user support, consensus, and participation in activities such as requirements analysis, usability testing, and acceptance test planning.

Developers have an important role in the development of testing goals and policies. (Recall that at TMM level 2 there is no requirement for a dedicated testing group.) They serve as members of the goal/policy development teams. As representatives of the technical staff they must ensure that the policies reflect best testing practices, are implementable, receive management support, and support among technical personnel. The activities, tasks, and responsibilities for the developers/testers include:

• Working with management to develop testing and debugging policies and goals.

• Participating in the teams that oversee policy compliance and change management.

• Familiarizing themselves with the approved set of testing/debugging goals and policies, keeping up-to-date with revisions, and making suggestions for changes when appropriate.

• When developing test plans, setting testing goals for each project at each level of test that reflect organizational testing goals and policies.

• Carrying out testing activities that are in compliance with organizational policies.

Users and clients play an indirect role in the formation of an organization‘s testing goals and polices since these goals and policies reflect the organizations efforts to ensure customer/client/user satisfaction. Feedback from these groups and from the marketplace in general has an influence on the nature of organizational testing goals and policies. Successful organizations are sensitive to customer/client/user needs. Their policies reflect their desire to insure that their software products meet the customer‘s requirements. This allows them to maintain, and eventually increase, their market share of business.

Upper management supports this goal by:

• Establishing an organizationwide test planning committee with funding.

Ensuring that the testing policy statement and quality standards support test planning with commitment of resources, tools, templates, and training.

•   Ensuring that the testing policy statement contains a formal mechanism for user input to the test planning process, especially for acceptance and usability testing.

•   Ensuring that all projects are in compliance with the test planning policy.

• Ensuring that all developers/testers complete all the necessary posttest documents such as test logs and test incident reports.

Project managers support the test planning maturity goal by preparing the test plans for each