[Backport stable/8.0] Realistic example test #278
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
We are still finetuning this to a sensible value. I had flaky tests when using 30ms. Therefore it is increased to 50ms to solve the flaky tests. (cherry picked from commit fceedae)
When a process contains a call activity it will call another process instance. If we want to assert this process we need to create a new ProcessInstanceAssert object, with the process instance key of the called process instance. Thus far we had no way to do this, except for using inspections. This was a bit of a hassle. With this new method we can now assert that a process instance has called a different process and using extractingLatestCalledProcess we can obtain the assertions from this process. This fits the other extracting... methods we have for asserting over e.g. incidents. (cherry picked from commit 5e26c46)
All our tests contain very minimalistic processes in order to be able to test something very specific. These new tests contain a bigger process with lots of different types of elements. This would be more in line with a process our users will be testing. These tests can now serve as an example for users, as well as verifying our assertions will remain functional when testing more complex processes. (cherry picked from commit fd11b2e)
In our testing Utilities class we had some helper methods to send variables. These methods did not allow for sending message with variables. Now they do. Note: our testing Utilities are not exposed to users. There are no backwards compatibility concerns here. (cherry picked from commit 6b523d0)
Our utility method completeTask would look for any jobs with a specific elementId that were created. It would not filter out jobs that were already completed. Because of this, if a process passed an element multiple times, we were only able to complete one job. This fix filters out the jobs that were already completed. This way we can keep completing the task until there are no more jobs available. (cherry picked from commit 3f10e8b)
Merged
7 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Backport of #276 to
stable/8.0.relates to #273