Test Strategy
The test strategy describes our general test methodology. This includes how testing is used to manage product and project risks, the division of testing into levels, and the high-level activities associated with testing. The test strategy and the processes and activities described will be consistent with the test policy. It will provide the generic test entry and exit criteria for us or one or more programs.
As mentioned above, test strategies describe general test methodologies, which typically include:
Using risk-based testing, our test team analyzes the test basis to identify the test conditions.
Such as operational profiling, where our test team develops a model (based on actual or anticipated situations) of the environment in which the system exists, the inputs and conditions to which the system is subjected, and how the system should behave.
Such as quality characteristic-based, where our test team uses a predetermined set of test conditions, such as a quality standard (e.g., ISO 25000, which is replacing ISO 9126), a checklist, or a collection of generalized, logical test conditions which may relate to a particular domain, application or type of testing (e.g., security testing), and uses that set of test conditions from one iteration to the next or from one release to the next.
Process or standard-compliant strategies, such as medical systems subject to U.S. Food and Drug Administration standards, where our test team follows a set of processes defined by a standards committee or other panel of experts, where the processes address documentation, the proper identification and use of the test basis and test oracle(s), and the organization of our test team.Â
Using defect-based attacks, where our test team waits to design and implement tests until the software is received, reacting to the actual system under test.
Such as user-directed testing, where our test team relies on the input of one or more key stakeholders to determine the test conditions to cover.
Also known as extensive automation, where our test team uses various techniques to manage the risk of regression, especially functional and/or non-functional regression test automation at one or more levels.
Different strategies may be combined. The selected strategies will be appropriate to the organization’s needs and means, and we will tailor strategies to fit particular operations and projects.
The test strategy may also describe the following
- Integration procedures
- Test specification techniques
- Independence of testing
- Mandatory and optional standards
- Test environments
- Test automation
- Test tools
- Reusability of software and test work products
- Confirmation testing and regression testing
- Test control and reporting
- Test measurements and metrics
- Defect management
- Configuration management approach
- Roles and responsibilities
Test Policy
The test policy describes why an organization tests. It defines the overall objectives for testing that an organization wants to achieve. Our test management staff in collaboration with senior managers for the testing stakeholder groups will develop this policy.
In some cases, the test policy will be complementary to or a component of a broader quality policy. This quality policy describes management’s overall values and goals related to quality.
The test policy should address test activities for new development and maintenance. It may also reference internal and/or external standards for testing work products and terminology used throughout the organization.
