Testing, Verification &Validation ASSIGNMENT-3

James C. Helm TA: Kaushik Vedantham

SUBMITTED BY

SRAVANI KANNEGANTI

Discuss the Test Manager role. Give the titles for the four documents, two that the test manager modifies and two that the test manager is responsible for?

Test Manager Role:

The Role of Test Manager is who effectively leads the testing team. The role involves quality and test advocacy, resource planning and management, and resolution of issues that delay the test effort. To fulfill this role he must effectively implement a testing process while fulfilling the traditional leadership roles of a manager. This involves creating a test infrastructure that supports robust communication and a cost effective testing framework. The Test Manager is responsible for:

Defining and implementing the role testing plays within the organizational structure. Defining the scope of testing within the context of each release / delivery. Deploying and managing the appropriate testing framework to meet the testing mandate. Advocating the appropriate level of quality by the resolution of important Defects Advocating an appropriate level of testability focus in the software development process Implementing and evolving appropriate measurements and metrics. o To be applied against the Product under test. o To be applied against the Testing Team. Planning, deploying, and managing the testing effort for any given engagement / release. Managing and growing Testing assets required for meeting the testing mandate: o Team Members o Testing Tools o Testing Process Retaining skilled testing personnel.

The Test Manager must understand how testing fits into the organizational structure, in other words, clearly define its role within the organization.

Fig. Showing the role of test manager

The two documents that test manager Modifies are 1. Issues List 2. Change Requests Issues List: An Issues List contains a list of ongoing and closed issues of the project. The Issues List provides the Project Manager with a way to record and track problems, exceptions, anomalies, or other incomplete tasks requiring attention that relate to the management of the project2. Change Requests: Changes to development artifacts are proposed through Change Requests (CRs). Change Requests are used to document and track defects, enhancement requests and any other type of request for a change to the product. The benefit of CRs is that they provide a record of decisions and, due to their assessment process, ensure that change impacts are understood across the project.

The two documents that test manager responsible are 1. Test Plan 2. Test Evaluation Summary

Test plan: The purpose of the Test Plan is to outline and communicate the intent of the testing effort for a given schedule. The main objective is to gain the acceptance and approval of the stakeholders in the test effort. The plan must identify the items to be tested, the features to be tested, the types of testing to be performed, the personnel responsible for testing, the resources and schedule required to complete testing, and the risks associated with the plan.

Test evaluation summary: The Test Evaluation Summary organizes and presents a summary analysis of the Test Results and key measures of test for review and assessment, typically by key quality stakeholders. In addition, the Test Evaluation Summary may contain a general statement of relative quality and provide recommendations for future test effort1.

References:
1. Artifact: Test Evaluation Summary [Internet]. Available from: http://sce.uhcl.edu/helm/RationalUnifiedProcess/process/artifact/ar_tstev.htm 2. Artifact: Issues List [Internet]. Available from: http://sceweb.sce.uhcl.edu/helm/RationalUnifiedProcess/process/artifact/ar_issues.htm