Please enable JavaScript.
Coggle requires JavaScript to display documents.
Defect Management, 7 Key Rules, Fundamental Test Processes: repeat each…
Defect Management
Definition
-
-
-
-
S/w is difficult to understand, hard, slow
-
-
-
-
-
Management Reporting
-
-
Strategic info ro seniors: trends, problem systems
-
-
-
Defect Discovery Process
Find quickly before it becomes expensive
Defect discovered = when it is officially brought attention + acknowledged valid
Find defect before they become major problem
- Static Techniques
- Dynamic Techniques
- operational technique - as a result of failure
-
-
-
- Defect Cycles - 7 (31)
- Classes and repository (34)
- Types of defects (35)
Defect Attributes
- Defect ID
- Project Name
- Module Name
- Sub Module Name
- Priority
- Summary
- Description
- Status
- Phase
- Reported by/on
- Type
- Assigned to
- Severity
- CC to
Defect Tracking Tools
- Test Director
- Rational Clear Quest
- Bugzila
- Excel Sheet
7 Key Rules
Testing shows presence of defects.
As we test more, number of defects reduce (not eliminate)
Exhaustive testing is impossible. Prioritise using a risk based method. Test too little - not enough, test too much - to expensive. Therefore find TESTING EQUILIBIRUM
Early Testing - Start early in development life cycle not with the code. Test objectives of the Test Strategy
Maintaince phase: inventory of specifications, code, all manuals, training material
But Planning and req phase - CHEAP
Defect Clustering: They are not all over the system, they are clustered. Confined to a small number of modules. 805 of errors are focused in 20% of the modules
Pesticide Paradox: Bugs keep improving and pesticides keep up. Developments in the S/W erode perv effectiveness. Keep coming with new tests to keep up!
Testing is Content Dependent: Testing is enviromnent dependent. NASA needs 0.01% errors whereas e-commerece site 10 failures KLOC
Absence of Errors Fallacy: we may create a system and solve all errors, but the system still might not work.
Fundamental Test Processes: repeat each multiple times if needed, overlap or simultaneous
Test Planning
- Identify the objective of testing
- Scope, Test Approach, Resources, Test Policy & Strategy
- Schedule test analysis & design tasks
- Implementation, execution, evaluation, exit criteria
Test Design and Analysis
- Test Conditions: An item or event or component can be verified by one or more test cases eg func transaction, features
- Test Cases: Set of input values, execution preconditions, developed for a specific test condition to verify a specific requirement
- Review Test Basics and Test Objectives
- Identify & prioritize Test Conditions and associates data sets
- Test Conditions - Test Design Specifications
- Design Test Cases, Identify test data for these cases, design environmental setup, identify any required tools or infra
-
-
E = P x I
Expected impact of risk
Probability of risk becoming a problem
Impact in Dollars of Risk -> Problem
- Techniques
- Quality assurance
- Training and education (work force + customers)
- Methodology & Standards
- Defensive Design + Code