Tester’s Role in Software Development and Acquisition Best Practice By Gabriel Rodriguez Agenda Tester’s Role in Software Development and Acquisition Q&A Reference Copyright 2006-2007. MSQAA Federation Chapter. Test’s Role in Software Development and Acquisition Copyright 2006-2007. MSQAA Federation Chapter. Tester’s Role in software Development and Acquisition Test Engineers are usually responsible for: – Developing test cases and procedures Software testers need to develop test matrices to control the design of test cases. Software Testers need to design test cases based on effective testing techniques. Software testers need to design procedures based on the project needs. – Test data planning, capture, and conditioning Software testers need to plan test data to be used during test execution. Copyright 2006-2007. MSQAA Federation Chapter. Tester’s Role in software Development and Acquisition Test Engineers are usually responsible for: – Reviewing analysis and design artifacts Software testers need to review and analyze: – Requirement documents. – Functional Documents. – Design Documents. – Test execution Software testers are responsible for test execution based on testing milestones. Copyright 2006-2007. MSQAA Federation Chapter. Tester’s Role in software Development and Acquisition – – Utilizing automated test tools for regression testing Software testers are responsible to learn automated testing tools to simplify regression testing. Preparing test documentation Software testers need to prepare any necessary testware during the project: – Procedures. – Guidelines. Copyright 2006-2007. MSQAA Federation Chapter. Tester’s Role in software Development and Acquisition – – Defect tracking and reporting Software testers are responsible to: – Find Defects. – Report defects. – Verify and validate defect fixes. Other testers joining the team will focus on: Test execution. Defect reporting. Regression testing. Copyright 2006-2007. MSQAA Federation Chapter. Tester’s Role in software Development and Acquisition – The test team should be represented in: All key requirements. Design meetings, including: – JAD or requirements definition sessions. – Risk analysis sessions. – Prototype review sessions. Copyright 2006-2007. MSQAA Federation Chapter. Q&A Any questions… Copyright 2006-2007. MSQAA Federation Chapter. Reference CSQA study Guide 2006 Copyright 2006-2007. MSQAA Federation Chapter. Thank you… Copyright 2006-2007. MSQAA Federation Chapter.