Test Engineer Roles and Responsibilities:
In an IT Industry there is a designated role for each employee based on what part he is about to play in software development life cycle, here is the list of Roles and Responsibilities of a Test Engineer or Independent Validation and Verification Engineer or Tester. Some of the Roles and Responsibilities are collectively done with non testing resources. Most of the Roles are common but there are slight difference from organization to organization or from project to project.
In an agile or in waterfall model responsibility and roles are same but the time of accomplishing the task or timing of start and end may vary. Here is an exhaustive list of Testing Resource duty to be carried out in an IT Industry based on my experience and knowledge, if you these traits then you will be able to fulfill the Roles and Responsibilities of a Tester, Test lead in any project or organization:
1. Understanding the requirement - Generally done with Development team in the presence of Business Analyst
2. Get the query clarification done either technical or functional - Prepare query tracker and get it answered from Developer or Architect, Test Manager, Business Analyst
3. Understanding the Test Plan and Test Strategy document available for the project - Test Plan and Test Strategy is prepared by test manager or test co-ordinator or test lead in discussion with Architect, Dev Project Lead and Project Manager, in some cases BA is included for review
4. Knowing different teams like Development Lead, Project/Module Lead, Project Manager, Test Manager, Onsite Co-ordinator, Off-shore team, Non-functional testing team, Configuration Management Team, Respective developer
5. Understanding basic Non Functional Requirements is added plus
6. Test Scenario preparation and getting it reviewed by Peers, Test Lead
7. Test Case design and Maintenance
8. Getting Test case Reviewed by Peers, Test Lead and BA- Business Analyst
9. Doing peer test case review
10. Requirement to Test Case Mapping - TL (Test Leads) do in some project and getting it reviewed
11. Defect Logging , Defect verification, Defect closure
12. Either TL or Tester generally do defect assigning task which is called as defect triage
13. Test Lead or Sr.Tester prepares defects list based on sevirity, priority, status based report
14. Test Execution and results capturing like logs, screen shots, request response, event/state transition details and attaching to each test case
15. Regression testing during each new build after new deployment
16. Smoke testing during start of test Execution
17. Sanity testing before starting function or non functional through testing
18. TL to publish Regression/Smoke/Sanity report and test execution report based on test status, maintenance different test suit for each phase of testing and also each level of testing should have different test suits (To verify at later stage what cases were tested at each phase and each level)
19. TL along with Testers prepare for internal/pre demo after testing is completed and met the exit criteria, get review from BA, PL, PM
20. Actual Demo with client or stake holders along with BA and Dev team
21. Backlog to be published and participate in retrospective or feedback (usually in agile)
22. Aid Automation and NFT-Non Functional Testing team by sharing relevent data, explaining scenarios to be considered (TL to play this role)
23. Once each build is tested, TL should ensure providing sign-off
24. TL or Sr. Tester to initiate DP-Defect prevention meeting at regular intervals with Technical, Functional, Architect and Leads
25. RCA to be done generally by TL and BA, PL, Architect
26. Maintenance and publishing DP and RCA outcome
27. Automation result publishing and NFT report publishing
28. Attending and doing active participation in weekly or daily status meeting
29. TL generally performs regular CPR(Check Point Review) Meeting with Test Manager, Project Manager
30. Frequent Test Data, Automation Result Review from Functional team
31. Additionally some of the Sr. Testers do white box testing before smoke testing
32. Aid development team during defect fixing, help to recreate issue in their environment or system, coordinate with them on the scenarios which had issue
33. For Test Automation lead, it's necessary to conduct Framework review meeting (DAR-Design Analysis Review) when designing or moving to New Framework or while doing major update to existing framework
34. Tester and TL should proactively do mentoring, knowledge sharing and give sessions and also involve or nominate themselves for new testing related training
35. TL and Sr.Tester should have basic knowledge of build and deployment
36. Tester, Sr. Tester, TL has to play equal role in maintenance and enhancement of testing artifacts , mapping documents, environment list publishing
37. Every tester should be aware of different testing levels like functional acceptance testing, quality assurance testing or customer acceptance testing, system testing
38. Testers had played a vital role in doing Impact Analysis which was missed if in case through the value chain of software life cycle by Functional and Development teams
39. Sr.Tester, TL do have a role during Gap Analysis
40. Tester , Sr. Tester, TL should know the estimation techinques based on complexity, impact considering overall time needed to complete test life cycle for that module
41. Testers should have basic knowledge on defect life cycle and also clear idea on severity , priority
42. Tester should demand and understand the major milestone set for testing and as a project overall, should be aware of goal of the project and time frame, they should know the testing life cycle in detail before starting any module. Tester should be aware of project methodology like it's Agile or Waterfall
2. Get the query clarification done either technical or functional - Prepare query tracker and get it answered from Developer or Architect, Test Manager, Business Analyst
3. Understanding the Test Plan and Test Strategy document available for the project - Test Plan and Test Strategy is prepared by test manager or test co-ordinator or test lead in discussion with Architect, Dev Project Lead and Project Manager, in some cases BA is included for review
4. Knowing different teams like Development Lead, Project/Module Lead, Project Manager, Test Manager, Onsite Co-ordinator, Off-shore team, Non-functional testing team, Configuration Management Team, Respective developer
5. Understanding basic Non Functional Requirements is added plus
6. Test Scenario preparation and getting it reviewed by Peers, Test Lead
7. Test Case design and Maintenance
8. Getting Test case Reviewed by Peers, Test Lead and BA- Business Analyst
9. Doing peer test case review
10. Requirement to Test Case Mapping - TL (Test Leads) do in some project and getting it reviewed
11. Defect Logging , Defect verification, Defect closure
12. Either TL or Tester generally do defect assigning task which is called as defect triage
13. Test Lead or Sr.Tester prepares defects list based on sevirity, priority, status based report
14. Test Execution and results capturing like logs, screen shots, request response, event/state transition details and attaching to each test case
15. Regression testing during each new build after new deployment
16. Smoke testing during start of test Execution
17. Sanity testing before starting function or non functional through testing
18. TL to publish Regression/Smoke/Sanity report and test execution report based on test status, maintenance different test suit for each phase of testing and also each level of testing should have different test suits (To verify at later stage what cases were tested at each phase and each level)
19. TL along with Testers prepare for internal/pre demo after testing is completed and met the exit criteria, get review from BA, PL, PM
20. Actual Demo with client or stake holders along with BA and Dev team
21. Backlog to be published and participate in retrospective or feedback (usually in agile)
22. Aid Automation and NFT-Non Functional Testing team by sharing relevent data, explaining scenarios to be considered (TL to play this role)
23. Once each build is tested, TL should ensure providing sign-off
24. TL or Sr. Tester to initiate DP-Defect prevention meeting at regular intervals with Technical, Functional, Architect and Leads
25. RCA to be done generally by TL and BA, PL, Architect
26. Maintenance and publishing DP and RCA outcome
27. Automation result publishing and NFT report publishing
28. Attending and doing active participation in weekly or daily status meeting
29. TL generally performs regular CPR(Check Point Review) Meeting with Test Manager, Project Manager
30. Frequent Test Data, Automation Result Review from Functional team
31. Additionally some of the Sr. Testers do white box testing before smoke testing
32. Aid development team during defect fixing, help to recreate issue in their environment or system, coordinate with them on the scenarios which had issue
33. For Test Automation lead, it's necessary to conduct Framework review meeting (DAR-Design Analysis Review) when designing or moving to New Framework or while doing major update to existing framework
34. Tester and TL should proactively do mentoring, knowledge sharing and give sessions and also involve or nominate themselves for new testing related training
35. TL and Sr.Tester should have basic knowledge of build and deployment
36. Tester, Sr. Tester, TL has to play equal role in maintenance and enhancement of testing artifacts , mapping documents, environment list publishing
37. Every tester should be aware of different testing levels like functional acceptance testing, quality assurance testing or customer acceptance testing, system testing
38. Testers had played a vital role in doing Impact Analysis which was missed if in case through the value chain of software life cycle by Functional and Development teams
39. Sr.Tester, TL do have a role during Gap Analysis
40. Tester , Sr. Tester, TL should know the estimation techinques based on complexity, impact considering overall time needed to complete test life cycle for that module
41. Testers should have basic knowledge on defect life cycle and also clear idea on severity , priority
42. Tester should demand and understand the major milestone set for testing and as a project overall, should be aware of goal of the project and time frame, they should know the testing life cycle in detail before starting any module. Tester should be aware of project methodology like it's Agile or Waterfall
This is a detailed checklist and some of which aren't sorted based on execution or delivery but it's worth to make note of these when you are going to an interview or when you update your CV or it helps when you are newly beginning your career in testing either as TL, IVV Engineer or as a Sr.Tester. Make note that, not all these activities are performed all the time in every project (organization) by a Tester.
#InfotainmentGuru blog by #PMH
Posts
No comments:
Post a Comment