IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Testing modules > Component testing > Automating tests using Ant scripts > Use Ant scripts for testing in headless WebSphere BPM

Overview of testing with Ant scripts in headless IBM BPM

If you have created component test projects, test suites, and test cases in IBM Integration Designer, you can use Ant scripts in conjunction with the serviceDeploy and wsadmin tools to automatically build, deploy, and test your projects in the headless (command line) batch processing environment of IBM BPM.

Although Ant scripts are not strictly required for running tests in a headless batch processing environment, there are several advantages to using them.

For example, Ant scripts enable you to automatically and simultaneously test numerous large applications that are inherently complex or constantly changing. They also allow you to run as many tests as you want or need in the off-hours, which reduces the load on computing systems and enables developers to focus on development activities when they are at work.

However, perhaps the most important reason for using Ant scripts is that you can configure an Ant script to automatically perform multiple tasks that would otherwise need to be performed manually, such as:

In WebSphere Integration Developer version 7.0 or later, component test projects are full-fledged SCA modules. This enables you to test your component test projects in the headless batch processing environment of IBM BPM and use the capabilities of the serviceDeploy and wsadmin tools. If you have pre-v7.0 component test projects that you want to test in headless IBM BPM, you can import them into IBM Integration Designer and a migration wizard will be automatically launched to enable you to convert the component test projects to version 7 SCA modules.

Although headless IBM BPM is the recommended test environment, there are several kinds of artifacts that cannot be successfully tested in this environment and you should use headless IBM Integration Designer instead. These artifacts are described in the "Limitations" topic.

Use Ant scripts for testing in headless IBM Process Server