we have two process applications AppA and AppB, each having its own process engine but sharing the process database. AppA contains the process model A, AppB contains the process model B. AppA does not contain the process B.
The process B expects some input variables when started and produces some output variables when it’s finished, i.e. it behaves like a method with an input and output parameters.
Process A has a Call Activity that calls the process B.
A quite common setting so far, I assume.
Now I’d like to write a unit test for the process A. But the test fails when the process B is called, since B is not a part of AppA.
I’d like to somehow mock/stub the call activity so that it does not try to start the process B but instead just puts some canned variables into the scope of process A (thus stubbing the process B). Is that possible (and how)? Do I have to dig deep into the internals of the process engine to do that?
I’ve seen these two threads with somewhat related questions but there the people do not “think in the same direction” as I do.
Thank you for any hints.