Installing and Running the Platform Test Environment
Oracle Communications Services Gatekeeper provides an entire suite of testing tools to help you develop your extensions quickly and efficiently. This chapter introduces the Platform Test Environment and describes installing and running it. It consists of:
The Platform Test Environment is a key part of the Platform Development Studio.
Figure 1-1 The Platform Test Environment in Context
The Platform Test Environment is a flexible, powerful tool, consisting of:
Application service test clients for most out-of-the-box communication services, using both the Web Services facade and the RESTful facade
PRM test clients for many operations covered by the Partner Relationship Management interfaces
Network simulators for most node types supported by the out-of-the-box communication services
A billing system simulator for use with the Diameter simulator
A real-time graphing budget monitor
Dual mode support:
Standalone with a Java Swing-based GUI
Console, in which the PTE’s functionality can be accessed using JMX, as, for example, from a unit test
MBean browser for performing Gatekeeper management tasks
Log browser for checking server logs
A JMS-based EDR/CDR/Alarm listener
JNDI browser
Database browser for interacting with the database
Real-time duration test graphing
SLA editor
Embedded TCP Monitor
Easily extendable architecture
An example application test client for use with the example communication service
An example network simulator for use with the example communication service
A set of SPIs that allows your modules to interact with the PTE
A framework for building unit tests, including:
A base test class, derived from JUnit
Mechanisms that simplify connecting to the Platform Testing Environment
An example test case for use with the example communication service
Installing and Running the Platform Test Environment
The Platform Test Environment is automatically installed when you install Oracle Communications Services Gatekeeper. In standard installations, it is found in the <bea_home>/wlng_pds400/pte directory. Before you use the PTE, you must have:
Used the setWLSEnv script in <bea_home>/wlserver_10.3/server/bin or set the equivalent path so that you have access to the Ant 1.6.5 installation that comes with WLS.
To start the PTE in GUI mode, type ‘ant run’ in a command window in the PTE directory.
To start the PTE in console mode, type ‘ant console’ in a command window in the PTE directory.
WARNING:
Compatibility between the settings of this version of the PTE and any future versions is not guaranteed.
