Team Lead Responsibilities:
Test Lead is responsible to understand and document testing requirements, provide test estimates, create and review test cases, execute and review test results, create and submit test reports to stake holders.
a) Understand and analyze Business, Functional, Technical and UI (User Interface) requirements of the project/release.
b) Provide Test Estimates for the types of testing carried out. It could be for Assembly and/or APT (Application Product Test) and/or IPT (Integration Product Test) and/or Performance Test. In bigger projects/release each of these testing types will have a different Test Lead. In smaller projects/releases a single test lead may support more than one of these testing types.
c) Provide hardware and software requirements based on the testing being carried out. APT (Application Product Test) and IPT (Integration Product Test) will have a different set of Hardware requirements and additional software requirements compared to Performance Testing.
d) Creates Test Strategy and Test Approach document for releases, gets it reviewed by required stake holders and keeps updating these documents as and when the changes are required.
e) Work with Application, Technical Architects, Business Analysts and other project stake holders to estimate, plan and execute Assembly and/or APT (Application Product Test) and/or IPT (Integration Product Test) and/or Performance Test. They are also responsible to support and co-ordinate during UAT (User Acceptance Test) and ORT (Operations Readiness Test).
f) Review test deliverables, defects, test results created by team members.
g) Create reports (daily status reports and weekly reports) and create testing metrics as requested by senior management.
h) Manage Testers work (during test plan and test execution), ensure testing is completed on time and within budget, resolve conflicts arising between team members or with external team members, keep team members motivated.
i) Identify risks and provide mitigation plan. Escalate issues on timely manner to management.
j) Ensure testing team is following testing standards, guidelines, and testing methodology as documented in Test Approach.
k) Ensures Entry criteria are met before starting with testing.
l) Ensure Exit Criteria is met and communicates the same to required stake holders. Creates and Signs-off on Test Closure Form (also known as Test Closure Memo) and obtains the approval from the required project/release stake holders.
m) Ensures deliverables are created as per Quality Management practices followed by the company or as outlined for the project/release. Participate in QA (Quality Assurance) reviews and provides required support and clarifications as need for the reviewers.
n) Ensures all the testing deliverables and reports are version controlled and are accessible for testing team and other privileged users.
No comments:
Post a Comment