Software Testing Lifecycle Practice

1. Software Testing Lifecycle Practice Yujuan dou(???) douyujuan@163.com MSN:douyujuan@sina.com 13858191626

2. Whole Course Plan 10 hours in total:3 classes, 2 Labs Test planning (2 hours, one time, class) Test Case Design(2 hours ,one time, class) Test Execution and Defect Tracking(4hours,2 times, in the lab) Test Reporting(2hours , one time, Class)

3. Home Work Draft a test plan for testing the Work log System (Group List) Delivery the test cases for Work Log Summarize the test results and deliver a test report Home work delivery: douyujuan@163.com or xzhu@zju.edu.cn

4. The First Class Plan Introduction of Whole Class Plan Test Planning Work log System introduction

5. Benefits of Test Plan Forms a contract between testers and project team Avoids random testing and missed features Optimizes resources

6. Key Points in Test Planning Test objective Test Scope Test Strategy Establish a team and defining roles Estimate a test timeline

7. Key Points-con. Risk Analysis Assumptions & Constraints Developing test plan detail Test cycles Test scenarios Test Cases

8. The forenamed information should be covered in all test plans. If for any reason a heading is not applicable, it should still be included in the plan, with a notation that it is not applicable.

9. Statement of Objective To describe why the testing is being performed and what will be accomplished as a result by this testing effort. for example �to ensure that the application will be able to recognize all financial periods that will be produced by the new functionality, and that all other processing is unaffected�

10. Tips and Techniques Itemize the objective Write the objectives in a measurable statement Prioritize Define the completion criteria for each objective

11. Test Scope What is to be included in the testing effort and what is to be excluded Features included Features not included Software Decomposition Client-Specific Requirement

12. Software Decomposition Identify what will be covered in the test plan including: Functions Transactions Reports Interfaces Error handling Downstream impacts

13. For example The next transaction/process in sequence should be part of the scope of the test effort. For example: if changes are made to the buy transaction, the settlement transaction and the buy cancel transaction should be tested, too. Documentation (on-line help)

14. Test Strategy Documents how the test will be executed. Include: Test Approach Test Environment and Test Requirements Test Techniques Test Team Team Preparation: knowledge transfer/training Simulation of Missing Units

15. Test Approach the overall method to conducting the test. Includes: Types of Testing Specify the types of testing: integration or system testing. and non-functional quality attributes such as performance, reliability, usability etc.

16. Test Approach-con. Testing Methods Specify the various testing methods (black box testing, GUI testing, system flow, database etc,) and the strategy of testing. The method of analyzing the test results are also to be documented. Indicate the test coverage if any. Identify the tools for defect tracking. Automated and Manual Tests Specify the tests which are automated and the tests that will be carried out manually.

17. Test Environment Where and under what conditions will testing take place. Is it in pilot of production, batch or on-line, mainframe or PC based, etc

18. Establish a Team and Defining Roles Specifies resources for each task Assigns tasks based on unique skill set Communicates objectives of testing effort

19. Participants Project Managers SQA managers Team Leaders SQA Specialists IT Representatives Clients Vendors Users Business analysts

20. Estimate a Test Timeline Development effort (software size) Percentage of new design Software complexity Technology platform Documentation quality Requirements stability Available resources

21. Risk Analysis Business Risk External Dependency Organizational Planning Technological

22. Assumptions & Constraints Assumptions are suppositions about things that may or may not happen in the future. Constraints are limitations that must be worked around to manage the test effort Organizational resources Business/Legal Cost ,technical, schedule/timing/dependency

23. Developing test plan detail Test cycles Test scenarios Test Cases

24. Sample Test Plan A typical Test Plan may have the following sections: Test Plan identifier: A unique name or number, useful if you store all documents in a database. Introduction: Include references to all relevant policy and standards documents, and high-level product plans. Test items: A test item is a software item (function, module, feature, etc) that is to be tested. List them all, or refer to a document that lists them all. Include references to specifications (e.g. requirements and design) and manuals. Features to be tested: Cross-reference them to test design specifications. Features not to be tested: Which ones and why not.

25. Sample Test Plan-con. Approach: Describe the overall approach to testing: who does it, main activities, techniques, and tools used for each major group of features. How will you decide that a group of features is adequately tested? Item pass/fail criteria: How does a tester decide whether the program passed or failed a given test? Suspension criteria and resumption criteria: List anything that would cause you to stop testing until it�s fixed. What would have to be done to get you to restart testing? What tests should be redone at this point?

26. Sample Test Plan-con. Test deliverables: List of all the testing documents that will be written for this product. Testing tasks: List all tasks necessary to prepare for and do testing. Show dependencies between tasks, special skills (or people) needed to do them, who do each, how much effort is involved, and when each will be done. Environmental needs: Describe the necessary hardware, software, testing tools, lab facilities, etc. Responsibilities: Name the groups (or people) responsible for managing, designing, preparing, executing, witnessing, checking, fixing, resolving, getting you the equipment, etc.

27. Staffing and training needs: How many people you need at each skill level, and what training they need. Schedule: List all milestones with dates, and when all resources (people, machines, tools, and facilities) will be needed. Risks and contingencies: What are the highest risk assumptions in the test plan? What can go sufficiently wrong to delay the schedule and what will you do about it? Approvals: Who has to approve this plan?