How do we reason our way to a Message publishing test?

Testing the message publishing endpoint requires a sophisticated chain.

1. It needs a model with a message catch event (model characteristic dependency).
2. The test has to deploy the model and create a process instance.
3. It needs to publish a message with the correct message name.
4. 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.

Start by reading the existing testing logic for Job Activation / Completion and compare its model-characteristic, deployment, process-instance, action, and completion assertions with message publishing. Then determine how message names and correlation variables fit the generated test flow; done means an implementable path for publishing and correlation tests.