Running Test Assertions

Unit tests focus on testing small units of work, which in TIBCO ActiveMatrix BusinessWorks™ maps to individual sub-processes. Ideally this is done in a standalone manner, with no touchpoints or dependencies on other components or interfaces. This is distinct from interface or system testing which would test the service or operation as a whole. Interface tests are run using other tools such as SOAP UI.

By design, ActiveMatrix BusinessWorks™ test assertions don't test the top-level process - they only test sub-processes. For example, if you had an EMS receiver as the start of a top-level process this would require an interface to EMS to run the tests which creates a dependency.

While test assertions have been available in previous versions of ActiveMatrix BusinessWorks, these instructions are specific to ActiveMatrix BusinessWorks 6.5.0 which introduced the ability to run unit tests in isolation, i.e. just test individual sub-processes using Maven without having to start the whole service. ActiveMatrix BusinessWorks 6.5.0 also introduces new capability around unit test reporting and test coverage reporting.