Cisco Cisco Computer Telephony Integration Option 8.5 Guía Del Desarrollador
Chapter 4 Building Your Application
Testing CTI Applications
4-4
Cisco ICM Software CTI OS Developer’s Guide Release 6.0(0)
•
C++. The CTI OS Client Interface Library for C++ is the appropriate choice
for building a high-performance application running on a Windows platform
in a C++ development environment. The C++ CIL is distributed as a set of
header files (.h) that specify the class interfaces to use and statically linked
libraries (.lib) that contain the compiled implementation code. These
components are not appropriate for non-Windows environments.
for building a high-performance application running on a Windows platform
in a C++ development environment. The C++ CIL is distributed as a set of
header files (.h) that specify the class interfaces to use and statically linked
libraries (.lib) that contain the compiled implementation code. These
components are not appropriate for non-Windows environments.
•
Java. The CTI OS Java Client Interface Library (Java CIL) is an appropriate
choice for non-Microsoft (typically UNIX) operating systems, as well as for
browser based applications.
choice for non-Microsoft (typically UNIX) operating systems, as well as for
browser based applications.
Testing CTI Applications
Testing is often characterized as the most time-consuming part of any application
development process.
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.
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.
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.
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.