Download presentation
Presentation is loading. Please wait.
Published byEmmeline Strickland Modified over 8 years ago
1
Certified Software Tester How To Build a Testing Project, Part 1
2
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Building a testing project Case Study Agenda
3
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Building a testing project
4
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Steps to build a testing project 1. Assessing Project Plan − Assess Project Estimate − Assess Development Process 2. Building a Software Testing strategy − Establishing a testing Policy − Establishing a test strategy Building a testing project
5
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Steps to build a testing project 3. Establishing a Software Testing Methodology − Acquire and study the test strategy − Determine the type of development project − Determine the type of Software System − Determine the Project scope − Identify the Tactical Risks − Determine When Testing Should Occur − Build the System Test Plan (Test Tactics) − Build the Unit Test Plan Building a testing project
6
Copyright 2006. MSQAA Federation Chapter Certified Software Tester 1. Assessing Project Plan If information technology does not determine the order in which they deliver completed pieces of software. It is impossible to schedule and conduct appropriate tests. The development team defines and documents the requirements for implementation purposes, and the test team uses those requirements for the purpose of testing the system. Assess Project Estimate: Project estimate is performed by Project Managers Building a testing project
7
Copyright 2006. MSQAA Federation Chapter Certified Software Tester 1. Assessing Project Plan Assess Development Process The traditional six phases of the software development life cycle are: − Initiation – Phase 1 − Definition – Phase II − System Design – Phase III − Programming and Training – Phase IV − Evaluation and Acceptance – Phase V − Installation and Operation – Phase VI Building a testing project
8
Copyright 2006. MSQAA Federation Chapter Certified Software Tester 1. Assessing Project Plan Assess Development Process Keep in mind that some projects may tweak the standard software development life cycle to meet their own needs. Building a testing project
9
Copyright 2006. MSQAA Federation Chapter Certified Software Tester 2. Building Software Testing Strategy Establishing a Testing Policy A testing policy is management’s definition of testing for a department Testing policy should be the cornerstone of the test plan A good practice is for management to establish the testing policy for the IT department, then have all members of IT management sign that policy as their endorsement and intention to enforce that testing policy. Criteria of the testing policy: − Definition of Testing − Testing System − Measurement of testing − Testing Standards Building a testing project
10
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Testing Policy Example Building a testing project
11
Copyright 2006. MSQAA Federation Chapter Certified Software Tester 2. Building Software Testing Strategy Establishing a Test Strategy The strategy must address the risks and present a process that can reduce those risks. The components are: − Test Factor –The test factors are not risks, they are attributes of the software that if they are wanted and not present, pose a risk to the success of the software and thus constitute a business risk. − Test Phase – Phase of the systems development life cycle. Building a testing project
12
Copyright 2006. MSQAA Federation Chapter Certified Software Tester 2. Building Software Testing Strategy Establishing a Test Strategy Test Factors: − Correctness − File Integrity − Authorization − Audit trail − Continuity of Processing − Service levels − Access control − Compliance − Reliability − Ease of use Building a testing project
13
Copyright 2006. MSQAA Federation Chapter Certified Software Tester 2. Building Software Testing Strategy Establishing a Test Strategy Test Factors: − Maintainability − Portability − Coupling − Performance Ease of operation Test Phase: − The test phase will vary. For example the test phases in a traditional waterfall life cycle methodology will be different from the phases in a Rapid Application Development methodology Building a testing project
14
Copyright 2006. MSQAA Federation Chapter Certified Software Tester 2. Building Software Testing Strategy Establishing a Test Strategy The four steps to develop a customized test strategy are: − 1- Select and Rank Test Factors − 2.- Identify the system development phases − 3.- Identify the Business Risks associated with the System under Development − 4- Place Risks in the Matrix Building a testing project
15
Copyright 2006. MSQAA Federation Chapter Certified Software Tester 3. Establishing a Software Testing Methodology Acquire and study the test strategy The test strategy is normally developed by a team very familiar with the business risks associated with the software In this study the test team should be asking: − What is the relationship of importance among the test factors? − Which of the high-level risks are the most significant? − What damage can be done to the business if the software is not completed on time? Building a testing project
16
Copyright 2006. MSQAA Federation Chapter Certified Software Tester 3. Establishing a Software Testing Methodology Determine the Type of Development Project The type of project refers to the environment/methodology in which the software will be developed − Traditional System Development − Iterative development/prototyping/CASE − System maintenance − Purchased/contracted software Building a testing project
17
Copyright 2006. MSQAA Federation Chapter Certified Software Tester 3. Establishing a Software Testing Methodology Determine the Project Scope The project scope refers to the totality of activities to be incorporated into the software system being tested- the range of system requirements/specifications to be understood Building a testing project
18
Copyright 2006. MSQAA Federation Chapter Certified Software Tester 3. Establishing a Software Testing Methodology Identify the Tactical Risks Strategic Risks are the high-level business risks faced by the software systems; tactical risks are subsets at a lower level of the strategic risks Tactical risks are divided into three categories: − Structural risks − Technical risks − Size risks Building a testing project
19
Copyright 2006. MSQAA Federation Chapter Certified Software Tester 3. Establishing a Software Testing Methodology Determine When Testing Should Occur Testing can and should occur throughout the phases of the project − Requirements − Design − Program (Build/Construction) − Test Process − Installation − Maintenance Building a testing project
20
Copyright 2006. MSQAA Federation Chapter Certified Software Tester 3. Establishing a Software Testing Methodology Build the System Test Plan A tactical test plan must be developed to describe when and how testing will occur. This test plan will provide background information on the software being tested, on the test objectives and risks, as well as on the business functions to be tested and the tests to be performed. Building a testing project
21
Copyright 2006. MSQAA Federation Chapter Certified Software Tester 3. Establishing a Software Testing Methodology Build the System Test Plan (Test Tactics) Test Plan Testing Techniques Testing Tools Note: More details on this phase will be covered on ‘Building a Testing Project Part 2’ presentation. Building a testing project
22
Copyright 2006. MSQAA Federation Chapter Certified Software Tester 3. Establishing a Software Testing Methodology Build the Unit Test Plan During internal design, the system is divided into the components or units that perform the detailed processing. Each of these units should have its own test plan. Building a testing project
23
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Testing Life Cycle Once a testing methodology has been established, the test team should rely on the testing life cycle. The testing life cycle is comprised of the following processes: Risk Analysis Planning Process Test Design Test Execution Defect Tracking and Management Quantitative Measurement Test status and reporting Building a testing project
24
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Case Study Based on Testing Life Cycle
25
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Risk Analysis- Assessing Project Plan
26
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Project Plan Case Study
27
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Test Planning- Testing Policy
28
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Testing Policy Case Study
29
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Risk Analysis - Test Strategy
30
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Test Strategy Case Study
31
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Test Strategy Case Study
32
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Test Strategy Case Study
33
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Testing Policy Case Study
34
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Testing Policy Case Study
35
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Risk Analysis- Traceability Matrix
36
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Traceability Matrix Case Study
37
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Test Planning - Test Plan
38
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Test Plan Case Study
39
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Test Planning - QA Schedule
40
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Test Plan-QA Schedule Case Study
41
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Test Design- Test Matrix, Test Data, Test Cases, Peer Reviews
42
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Test Matrix Case Study
43
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Test Cases Case Study
44
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Peer Reviews Case Study
45
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Test Execution- Test Readiness Review, Test Execution Log
46
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Test Readiness Review Case Study
47
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Test Execution Log Case Study
48
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Defect Tracking and Management- Triage Reports, Defect Tool
49
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Triage Report Case Study
50
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Defect Tool The customer provided his own defect tool. Defects were tracked using Microsoft Share Point. Case Study
51
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Test Reporting- Test Results Reports, Status Reports
52
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Test Report – Part 1 Case Study
53
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Test Report – Part 2 Case Study
54
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Test Report – Part 3 Case Study
55
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Weekly Status Report Case Study
56
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Post Mortem
57
Copyright 2006. MSQAA Federation Chapter Certified Software Tester Post Mortem Case Study
58
Copyright 2006. MSQAA Federation Chapter Certified Software Tester CSTE Preparation guide Effective Methods for Software Testing Reference
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.