Table Of Contents
IP Communications System Test Results
This document provides a summary of the results of the IP Communications System Test Release 4.2 for IPCC Enterprise and IPT. This document contains the following sections:
Cisco Systems validates IPC systems by designing, installing, configuring, and testing IPC hardware and software to achieve a predictable, effective, and reliable system. The intent of system testing is to validate the seamless interoperability and stability of the components that make up a complete and optimized IP Communications Systems Test Release.
Testing performed in the IP Communications System Test includes (but is not limited to) the following:
•Installation, Upgrade, and Usability Testing—To verify software installation and upgrades at the system level and usability for system components
•End-to-End Functionality Testing—To verify the end-to-end functionality of system components
•Basic Functionality and Feature Testing—To verify basic call flows and component features
•Customer Assurance Program (CAP) Scenario Testing—To recreate and test CAP scenarios based on TAC input
•Interoperability Testing—To verify the interoperability among system components
•Scalability Testing—To verify system functionality during scalability tests
•Performance, Load, and Stress Testing—To verify system functionality during performance, load, and stress tests
•Failover, Recovery, and Redundancy Testing—To verify system behavior during failover and recovery, and behavior in redundant configurations
Tested Systems and Scenarios
The System Test Architectural Reference Manuals provide information about the components and configurations that have been tested and verified as part of a given IP Communications System Test Release.
For information about the components, configurations, and environment tested in Release 4.2, refer to one of the following documents:
The results of the system tests for IPT and IPCC are presented in the following documents:
These documents list all the tests that were performed on the system. The tables in these documents include the following information:
•Title—Title of the test.
•ID—Identifier for the test.
•Description—Description of the purpose of the test.
•Features Tested—Component feature tested.
•Status—Result of the test and any defects related to the test case. Possible values are:
–Passed—Test case passed as described in the table.
–Failed—Test case failed and the reason is described in the listed defect.
–Passed with exception—Test case as described passed but an anomaly occurred that was not directly related to the functionality being tested. Possible anomalies are as follows:
The test steps were modified based on the actual feature implementation.
The test setup was modified based on the actual feature implementation.
The test results did not exactly match what was expected although the feature performed as required.
•Defects—Identifier for any defect that was opened against the test. If you have an account with Cisco.com (Cisco Connection Online), you can use the Bug Toolkit to view information about defects.
To access the Bug Toolkit, perform either of these actions:
–Go to this URL: http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl
–Log in to Cisco.com, click Technical Support, click Tools & Utilities, and then click Software Bug Toolkit under Troubleshooting Tools.