This project is read-only.

Test manager

About Tester Manager

The test manager leads a team of test coordinators or test managers. He is responsible for the planning, management and execution of the test process, on time and on budget and at the right quality, for multiple test levels or test types. He reports conformable to the test plan on the progress of the test process and the quality of the test object. This function is active throughout the TMap life cycle. The test manager, sometimes also known as overall test coordinator, is the role primarily responsible for creating the master test plan. In some cases, the role is combined to include quality assurance (QA) responsibilities, to integral test and QA manager.

MasterTestPlanTestLevels_1.png Management of master test plan and test levels
  • ‘Unnecessary double testing’
  • An important reason for a master test plan is preventing unnecessary double testing. The word ‘unnecessary’ is important in this context. As such, double tests are not a problem; often they cannot be avoided, and in some cases they are even mandatory. In a unit test, for instance, the same functionality will often be tested as in a system test, and various test cases will resemble each other. Part of the system test may also be repeated on purpose in the acceptance test, e.g. to check that everything works on the production-like infrastructure or within existing business processes. An example of ‘unnecessary double’ is when two test levels use a similar test design technique to derive and execute similar test cases.
  • Creating the master test plan.
  • The diagram below shows the overall order of and dependencies between the various activities. All activities may be executed several times, because the results of one activity may require a review of the previous one. As mentioned in the method, steps 4, 5 and 6 have an explicitly iterative nature:

  • Possible tasks*
  • The tasks as executed by the test coordinator
  • Creating, obtaining approval of and maintaining the master test plan
    • Risk assessment and strategy determination
    • Creating planning and estimate
    • Specification of organisation and infrastructure
    • Specification of procedures and standards.
  • Executing the master test plan within planning and budget
    • Recruiting and assessing employees
    • Day-to-day management of test activities
    • Setting up the organisation
    • The test functions and procedures are executed conformable to the structure specified in the master test plan
    • Executing work distribution
    • Establishing master test plans
    • Monitoring progress.
  • Maintaining external contacts
  • Internal quality management
  • Acknowledging, anticipating and reporting on project risks
  • Defining or advising on test policy
  • Execution of test process optimizing.
  • Master test plan; Test plan by which the various test levels are geared to one another. For more information according to the Master Test Plan see Hfst 5 Mastertestplan, managing the total testprocess.

Last edited Nov 6, 2009 at 8:21 PM by ClemensReijnen, version 4


No comments yet.