Test And Validation - Avaya Application Solutions Deployment Manual

Test and validation

After the risk level of the potential change has been assessed, the appropriate amount of testing
and validation can be applied.
how testing and validation may be applied to the five-level risk model.
Table 86: Testing and validation recommendations
Risk level
1
2
3
4
5
For changes with risk levels 1 through 3, two types of laboratory validation are important:
Feature and functionality testing
What-if analysis
Feature and functionality testing
Feature and functionality testing requires that you validate all configurations, modules, and
software with laboratory-generated traffic to ensure that the solution can handle the expected
traffic requirements. Create a test plan that validates configuration parameters, software
functionality, and hardware performance. Be sure to test behavior under real-world conditions,
including spanning-tree changes, default gateway changes, routing changes, interface flaps,
and link changes. Also validate the security and network management functions of the new
solution.
Table 86: Testing and validation recommendations
Recommendations
Requires laboratory validation of the new solution, including
documented testing, validation, and what-if analysis showing the
impact to existing infrastructure; completion of an operations support
document, backout plan, and implementation plan; and adherence to
the change process. Recommend solution pilots and a preliminary
design review prior to testing.
Requires laboratory what-if analysis to determine the impact to the
existing environment with regard to capacity and performance; test
and review of all routing changes; backout plan, implementation plan,
and adherence to change process; and design review for major
routing changes or backbone changes.
Requires engineering analysis of the new solution, which may require
laboratory validation; implementation plan and adherence to change
process.
Requires implementation plan and adherence to change process.
Optional adherence to change process.
High-Level process flow
demonstrates
Issue 3.4.1 June 2005 375