Service Validation and Testing
From IT Process Wiki
| diese Seite auf Deutsch |
|---|
ITIL Version: ITIL Version 3 (ITIL V3)
Process Objective: To ensure that deployed releases and the resulting services meet customer expectations, and to verify that IT operations is able to support the new service.
Part of: Service Transition
Process Owner: Test Manager
ITIL V3 vs. ITIL V2: Service Validation and Testing
- Service Validation and Testing is new process in ITIL V3; ITIL V2 covered some aspects of Release testing within Release Management but ITIL V3 provides considerably enhanced guidance
- Major additions in ITIL V3 are details on the various testing stages during Service Transition and descriptions of the corresponding testing approaches
Sub-Processes of Service Validation and Testing (ITIL V3)
- Test Model Definition
- Process Objective: To specify in detail how the Release will be tested and quality-assured. In particular, this process defines the testing concept and specific test cases to be used during Service Validation.
- Service Design Validation
- Process Objective: To ensure that an IT service meets its functionality and quality requirements and that the service provider is ready to operate the new service when it has been deployed.
- Release Component Acquisition
- Process Objective: To acquire the components of a Release and submit them to an initial assessment. This process ensures that only components which meet stringent quality criteria are allowed to enter the intensive testing phase.
- Release Test
- Process Objective: To test all Release Components and all tools and mechanisms required for deployment, migration and back out. This process ensures that only components which meet stringent quality criteria are deployed into the live productive environment.
- Service Acceptance Testing
- Process Objective: To verify if all conditions are met for the new service to be activated, and to obtain a binding consent from the customer that the new service fulfils the agreed Service Level Requirements.
