Testing the message publishing endpoint requires a sophisticated chain.
- It needs a model with a message catch event (model characteristic dependency).
- The test has to deploy the model and create a process instance.
- It needs to publish a message with the correct message name.
- It needs to assert that the process instance completes.
This looks very similar to the testing logic for Job Activation / Completion:
- Same prereqs: A model characteristic and specific value (job type / message name).
- Same preconditions: deploy, create.
- Similar action: publish / correlate (vs activate + complete).
- Same assertion: process completes.
This seems like it generalises is a similar way to activateJobs / completeJob.
Correlation is more sophisticated. It needs to start the process instance with a specific variable name + value, then it needs to populate the correlation call with the variable value.
Testing the message publishing endpoint requires a sophisticated chain.
This looks very similar to the testing logic for Job Activation / Completion:
This seems like it generalises is a similar way to activateJobs / completeJob.
Correlation is more sophisticated. It needs to start the process instance with a specific variable name + value, then it needs to populate the correlation call with the variable value.