Cisco Cisco Computer Telephony Integration OS 8.5 Developer's Guide

Page of 668
 
4-7
CTI OS Developer’s Guide for Cisco ICM/IPCC Enterprise & Hosted Editions Release 7.1(1)
 
Chapter 4      Building Your Application
Testing CTI Applications
Testing CTI Applications
Testing is often characterized as the most time-consuming part of any application 
development process. 
Developing a Test Plan
Testing CTI applications requires a detailed test plan, specific to the business 
requirements set forth in the requirements gathering phase of the project. The test 
plan should list behaviors (test cases) and set forth requirements to prove that each 
test case is successfully accomplished. If a test case fails, it should be investigated 
and corrected (if appropriate) before proceeding to the next phase of testing.
It is recommended that you perform (at minimum) the following test phases:
  •
Unit Testing. In a unit test, you ensure that all of the new code units can 
execute properly. Each component will operate correctly based on the input, 
and produce the correct output. An example of a unit test would be to 
‘stub-in’ or hardcode the expected screen-pop data, and ensure that all of the 
screens come up properly based on this data.
  •
Integration Testing. In an integration test, you ensure that all of the new 
components work together properly. The physical connections and data 
passing between the layers and servers involved in the system are tested. An 
example of an integration test would be testing your client application with 
the CTI OS server, to ensure that data can be passed correctly through the 
components. 
  •
System Testing. In a system test, you ensure that the correct application 
behavior is exhibited. An example of a system test would be to make a phone 
call to a VRU, collect the appropriate caller information, transfer the call to 
an agent, and ensure that the screen pop arrives correctly. 
  •
User Acceptance Testing.  In a user acceptance test, you ensure that your 
application has met all of the business requirements set forth by your analysis 
and design process. An example of a user acceptance test would be to try out 
your new application with real agents, and ensure that it satisfies their 
requirements.