In the previous chapter, you created the Tahiti application and ran it in your development environment to validate all the actions presented in the application page and the associated processes. This chapter contains some advice about how to test your application more thoroughly before putting it into production, and explains some of the considerations for setting up the environment required to support the application. Finally, it suggests some ideas for improving the application in future versions.
When you use a BPM solution to build a process-based application, you need to plan for testing, just like in any other software development process. The details of what testing is required and how you run the tests will depend on your corporate infrastructure and guidelines for acceptance testing to demonstrate that the application is acceptable to be installed.
Typically, testing is done at various levels such as unit test, workflow execution, and user acceptance testing.
Unit tests focus on the source code you write for your processes implementation, addressing each code unit separately.
When you use Bonita BPM, you typically write source code for the following artifacts:
Java code for connectors, actor filters, event handlers, or libraries included in process definitions. In the Tahiti application, you have not created any Java code.
Groovy scripts for REST API extensions and in various places in process definitions. ...