Testing solutions

You test solutions by submitting events to an Insight Server. You can use event sequences or a Java class named TestDriver.

Establishing a development environment involves setting up hardware and other infrastructure resources, and the project structure that is required by the development activities. Similar to the development environment, the testing environment must be designed to emulate the production environment as closely as possible.

When your environments are set up, you can begin your solution testing work. In a proof of concept or in early development, you might want to create a Java test client or use Insight Designer to submit events. Your final test environment must use your day-to-day message providers of your deployment environment to access the necessary data that is required to run the associated test cases. When the testing environment is different from the target environment to a significant degree (typically, in terms of size or capacity), some testing can be planned in the deployment environment. However, if you do test in the deployment environment you must coordinate the testing closely. When the solution is successfully deployed, it is important to continuously monitor the actual performance against your projections.

The following figure shows the choice between using a TestDriver class and creating a set of test files; the files can be run independently or as a test scenario. The TestDriver API includes the DebugReceiver interface to help you capture information for debugging and problem determination. First failure data capture (FFDC) services can also be configured to capture FFDC output. Insight Inspector can be used to analyze a recording of a solution that processes the events that you submit.

Before you use Insight Server in your test and target environments, consider the following issues to optimize your deployment.