Testing

Environmental Differences between Animation Testing and Deployment Testing

There are significant environmental differences between Animation testing in Composer and Deployment testing. Both types of testing are needed to adequately verify the components and services you build. The differences are detailed in the table below.

	Testing in Composer	Deployment Testing
OS	Win98 or WinNT or Win 2000.	WinNT or Sun Solaris.
Platform	JRE (Java Runtime Environment).	Application Server complete with JRE support for Failover, Security, Connection Mgt., etc.
Component or Service Startup	Directly from Composer.	By Service Triggers only (i.e., deployment Servlets or EJBs).
xObject access	From disk files.	From a JAR file in Application Server.
Runtime Context	Test individual components or components running within a service.	Always from within a service.
Service and Component Inputs	Input documents frequently come from sample XML documents on the local machine as well as DOMs from other services or components.	Input documents are passed into the services and components via Service Triggers, or DOMs from other services or components.
Project Variables for:* Log File Paths* DTD URLs* XSL URLs* Send Mail Server* XML Inter-change URLs	Usually point to locations on local machine (but could be on Servers or Web).	Should point to locations on production Servers and Web.
Testing Tools	In addition to Log actions, you can use dialog boxes (ECMAScript alert() function) to display runtime values.	No dialog boxes can be used.