Test Methodology

Overview of the V-Plan test methodology

soft tech global
We always have a solution

Presentation Contents and purpose

The following slide show will provide an overview of the V-Plan test process and will include background on What is the V-Plan methodology? What are the test stages in V-Plan? What are test phases and test cycles? What are Quality Gates? Why are they important and how do we use them? While this presentation will focus on the V-Plan model, which is Soft currently the industry standard STG are aware of the need to be prepared to deploy alternate test process. Please feel free to discuss your needs with us should be considering using other of test methodologies

soft tech global

We always have a solution

The V-Plan Test Methodology diagram

Business Case Requirements System Specifications Release Testing Acceptance Testing System Testing

System Design

Interface Testing

Component Design

Component Testing

Construct Component

soft tech global

We always have a solution

What is the V-Plan methodology

V-Plan is an industry accepted software development and deployment methodology. As such testing is only a part of this methodology. As you can see from the following diagram there are two wings of the process with elements in each wing being linked directly to a preceding phase in the alternate wing. It is these linkages that allow the project team to monitor and control the software development cycle and to ensure that the test phases support not only the development but also act as quality assurance into each subsequent phase of the development cycle. With V-Plan it is important to note that the results from each phase of testing provides the project governance with a basis to move forward and to produce a detailed and accurate risk analysis with which to control the project. It is these elements that make the V-Plan methodology the current industry standard.

soft tech global

We always have a solution

V-Plan Test Stages

The following chart provides a view of the three stages involved in the successful deployment of testing for the V-Plan methodology.

Solution Delivery Testing

Planning Requirements Strategy design Strategy sign-off Test schedule Resource plan Test cases Solution Testing Unit Testing Integration 1 Integration 2 Integration 3 Non-Functional User Acceptance Go-Live Prep Stress and Volume Operational acceptance Business readiness Compliance

Regression
Post Go-Live Process regression test Stress testing Volume Testing

soft tech global

We always have a solution

V-Plan Test Planning Phase

The primary testing for any solution is the second stage of the V-Plan test methodology which covers testing of the solution itself. Normally there are three distinct phases:Requirements: New configuration in an SAP implementation Test strategy document: For an SAP implementation this is normally Test schedule: Often seen as the chance for the business to evaluate Resource planning: Often seen as the chance for the business to evaluate

soft tech global

We always have a solution

V-Plan Integration Test Phases

The primary testing for any solution is the second stage of the V-Plan test methodology which covers testing of the solution itself. Normally there are three distinct phases:Unit / String test: New configuration in an SAP implementation are first tested as individual delta level to ensure their internal integrity. It is possible that a limited integration test covering the entry and exit touch points may be included as a string test. Integration testing: For an SAP implementation this is normally conducted in three cycles to allow for testing of the SAP deltas, integrations across interfaces with legacy systems and a final holistic integration test User Acceptance Testing: Often seen as the chance for the business to evaluate the solution there are a number of approaches to a successful UAT and the most suitable should be chosen and clearly stated in the project test strategy document

soft tech global

We always have a solution

V-Plan Go-live Test Phase

The primary testing for any solution is the second stage of the V-Plan test methodology which covers testing of the solution itself. Normally there are three distinct phases:Stress and volume testing: Separate to the functional testing conducted during the integration test phase stress and volume testing comes under the heading of nonfunctional testing. Stress testing identifies any degradation of service due to technical choke points while volume testing identifies service issues relating top process choke points. Operational acceptance testing: the operational acceptance testing phase provides the business with assurance that the live landscape is operational and ready to support the deployed solution. Testing ain the OAT phase may also include the support structure as well as disaster recovery Business readiness testing: A final chance for the business to conduct a series of tests to ensure that the localized landscape is also operational and could include the ability for selected users to sign-on, confirm security settings and access local soft tech global printers, scanners etc.
We always have a solution

Quality Gates Purpose and use

An essential component of the V-Plan methodology is the sue of Quality Gates. A Quality gate is a defined review point between each of the stages, phases and cycles of the test process. To ensure the quality of the testing conducted in each stage or cycle the entry it is important that the quality gates to be passed are agreed during the planning stage and should be an part of the project test strategy. A individual quality gate should contain the following minimum components: Entry Criteria Quality Gate Components Exit Criteria Agreed escalation process Agreed sign-off process

In addition ownership of each element of the quality gate and the quality gate components e.g. suitable documentation, agreed test coverage and defect levels should be agreed during the planning stage and included in the test strategy document. soft tech global
We always have a solution