Agile Software Test Strategy
Summary
Use this section to briefly describe the document purpose, scope and the approach in relation to the software under test.
________________________________________
Purpose
The purpose of a Test Strategy is to create a shared understanding of the overall approach, tools, targets and timing of test activities. Use this section to describe the context and the approach to assessing the quality of the developed software.
Guiding Principles
Describe the principles underlying the testing approach. Consider the following basic principle as a starting point:
Principle Description
Shared Responsibility Everyone is Responsible for Testing and Quality
Test Automation All types of tests (unit, integration, acceptance, regression, performance) should be automated. Manual testing will only be used for exploratory type testing.
Data Management Production data must be obfuscated before being used for testing
Test Management Test cases, code, documents and data will be treated with the same importance as production code.
Quality and Test Objectives
The following quality attributes have been identified as relevant and are used as a basis for the test approach in terms of priority and test targets.
Attribute Description Measure and Target Priority
Correctness Features and functions work as intended • 100% completion of agreed features
• Severity 1 defects = 0
• Severity 2 defects = 0
• Severity 3 defects < 5
• Severity 4 defects < 10 Must
Have
Integrity Ability to prevent unauthorised access, prevent information loss, protect from viruses infection, protect privacy of data entered • All access will be via HTTPS over a secured connection.
• User passwords and session tokens are encrypted. Must
Have
Maintainability How easy it is to add features, correct defects or release changes to the system. • Code Duplication < 5%