Process testing

Tips and how-tos for functional and performance testing of your automation projects.

Functional testing

Bonita Studio contains several features that you can use to verify your processes and their elements while the project is in development:

  • Connectors testing: Select the connector to test and open it.

  • Expressions testing: use the Evaluate feature of the Expression editor.

  • Process diagram validation: Right click on process in the project explorer and select Validate, or go to the Details panel, Validation status tab and click Refresh. The Details panel contains a list of warnings and errors indicating things to correct in the diagram. Click on a row in the list to highlight the relevant item in the diagram.

  • Process local run: Select the process pool and click on the Run icon of the studio coolbar. The processes are deployed in the embedded Tomcat, and made available in Bonita provided applications.

If you have already created your own actors for your lanes and human tasks, you need to map them to entities of your test organization before you run your processes. To do so:

  1. Create your test organization (see below)

  2. Select the process pool

  3. Click on the Configure icon of the Studio coolbar and configure the Actor mapping

Integration Testing

For Subscription editions only.

To write automated integration test scenarios for your automation project you can use the Bonita Test Toolkit. It provides powerful methods to execute all the steps of a process and check the corresponding outputs (statuses, business data, tasks used)

It can be used in any IDE and can be integrated into a Continuous Integration.

More information in the dedicated documentation: Bonita Test Toolkit

Performance testing

In addition to functional testing during development, we recommend that you monitor the system load. This will help evaluate the performance, so you can make your processes efficient.

When you have finished developing your process, we also recommend that you perform a load test with the expected number of simultaneous users of the project, and a realistic rate of use of the processes. This will help you evaluate the size of the platform (CPU, RAM, etc.) you will need when the project goes into production.