These documents described the system-level test cases executed on each of the following Cisco Unified Communications System Release 8.0(2) solutions:
–System Test Results for Contact Center: Cisco Unified Communications System, Release 8.0(2)
–System Test Results for IP Telephony: Cisco Unified Communications System, Release 8.0(2)
Test Results Information
Testing Objectives give information on the intent of system testing
The test results contain the following information:
•ID—Identifier for the test.
•Features Tested—Component feature tested.
•Case Title—Title of the test.
•Description—Description of the purpose of the test.
•Call Component Flow—Indicates the sequence of components involved in the test.
•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, you can use the Bug Toolkit to view information about defects.
To access the Bug Toolkit, go to this URL:
Cisco Systems validates Cisco Unified Communications System systems by designing, installing, configuring, and testing 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 Cisco Unified Communications System system.
Testing performed for Cisco Unified Communications System 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 re-create 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