Introduction
The Test strategy review workshop is conducted after the Solution blueprint review so that enough context is provided about the solution scope, solution design, and overall project goals to ensure that the workshop can be productive. The Test strategy workshop does not dictate a specific testing methodology; instead, it is designed to work with and evaluate a variety of testing approaches. The main objective of this workshop is to evaluate that the underlying principles of testing are being addressed.
Timing of the Test strategy review
Testing the solution is essential to the success of the implementation. The project’s test strategy provides the blueprint for the approach to testing and includes the high-level plan that will be followed to support the validation of the solution. A good test strategy drives the approach to the validation of the project solution from the start. The strategy should promote and enable the project to engineer quality into the solution rather than only being a check at the end of the project. To understand the specific requirements for this project’s test strategy, it is essential that you have a good understanding of the project scope and project risks. Setting the right validation and quality approach from the start of the project will help avoid missed opportunities toward keeping the solution on the right track. As such, we recommend that you conduct the Test strategy review soon after the Solution blueprint review workshop. Conducting the review early allows you to minimize the impact of issues that are found and identify risks before they become issues.
The Test strategy review also forms the basis of understanding for the planned test phases and timing, which will provide you with an overall context in which to provide guidance on testing. Typical questions that solution architects have regarding the Test strategy review process and the answers to those questions are as follows:
Question - A generic test strategy document is provided in our methodology. Is that enough to review?
Answer - A good, generic test strategy provides a framework. However, unless it has been mapped to your specific project (scope, risks, timeline) and the specific organization (requirements, constraints, and resources), it is not possible to identify the project-specific risks and issues.
Question - We are busy with project tasks, especially design and build, and our test strategy is being worked on. Can we postpone the workshop until later when we have completed the test strategy and it has been approved by all parties?
Answer - Postponing the review will also postpone early identification of risks. Likely, if the project is already in implement phase, some form of validation and testing is already being conducted or planned. Reviewing the draft test strategy document will help ensure that it is completed with review and recommendations for you to consider.