Posts

Software Quality Risks By Rex Black

1. Functionality 2. Performance 3. Reliability 4. Stress, Capacity and Volume 5. States 6. Transitions 7. Installation and Deinstallations 8. Operations 9. Maintenance and Maintainability 10. Regression 11. Usability and User Interface 12. Data Quality 13. Errors and Disaster Handling and Recovery 14. Date and Time Handling 15. Localization 16. Configuration and Compatibility 17. Networked, Internetworked and Distributed 18. Standards and Regulatory Compliance 19. Security 20. Timing and Coordination 21. Documentation

ISO 9126 - Software Quality Risks

1. Functionality 1.1. Suitability 1.2. Accuracy 1.3. Interoperability 1.4. Compliance 1.5. Security 2. Reliability 2.1. Maturity 2.2. Recoverability 2.3. Fault Tolerance 3. Usability 3.1. Learn ability 3.2. Understandability 3.3. Operability 4. Efficiency 4.1. Time Behavior 4.2. Resource Behavior 5. Maintainability 5.1. Stability 5.2. Analyzability 5.3. Changeability 5.4. Testability 6. Portability 6.1. Install ability 6.2. Replacibility 6.3. Adaptability 6.4. Conformance (e.g. conformance to particular db standard)

List of Critical Software Testing Processes

1. A Quality Risk Analysis Process 2. An Estimation Process 3. A Test Planning Process 4. A Team Building Process 5. A Test System Design and Implementation Process 6. A Test Release Process 7. A Test Execution Process 8. A Bug Reporting Process 9. A Test Results Reporting Process 10. A Change Management Process References Book: Critical Testing Process By Rex Black

Testing Strategy - What testing types to consider?

Image
Before we start testing for any project, we need to develop a testing strategy. Like any other strategy, it should include detail steps for achieving testing goal(s) and resources & timeline involved during the steps execution. The strategy should also include assumptions if there are any. All risks that might affect the strategy need to be identified. Identified risks need to be mitigated further by analyzing. This article describes a methodology for identifying risks involved in testing phases of a testing project, which can be used further to identify types of testing needed and effort required to test the product successfully. The matrix below provides mapping between testing phases and types of testing involves in those phases. Step 1: Go through every phase and types of testing and ask “What is the risk am I taking by not testing it?” Step 2: Fill the matrix cell with priority of the risk – “High”, “Medium” and “Low.” If testing is not required for the phase, mark the ce