New assertion for ProcessInstances: waitingForMessage or hasMessageSubscription(...) #29
Comments
|
@berndruecker While knowing/considering that ... assertThat(processInstance).isWaitingAt("MessageEvent_1");... already works, you would probably still like to see something more message oriented ... assertThat(processInstance).isWaitingForMessage("myMessage");... where myMessage is ... <message id="Message_1" name="myMessage"/>Correct? |
martinschimak
added a commit
that referenced
this issue
Sep 12, 2014
…'isNotWaitingFor' and helper methods 'send' Affects #29
martinschimak
added a commit
that referenced
this issue
Sep 12, 2014
… to easily send messages to specific process instances Affects #29
martinschimak
added a commit
that referenced
this issue
Sep 12, 2014
…erify process instances Affects #29
martinschimak
added a commit
that referenced
this issue
Sep 12, 2014
…erify process instances Affects #29
martinschimak
added a commit
that referenced
this issue
Sep 12, 2014
…o verify process instances Closes #29
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We could maybe add the possibility to send the message easily like with complete(task())
The text was updated successfully, but these errors were encountered: