Manage step params in MW test cases #280
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
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
In MW UI test cases, we explicitly check for a string with the complete signature of an execution trace in the stack trace.
(This is indirectly the reason for this failing test result: https://ci.eclipse.org/gemoc/job/gemoc-studio-integration/job/stepReturn/10/testReport/)
Until now, such parameters were not correctly provided to step objects, and thus not displayed. This changes with this other PR: eclipse/gemoc-studio-modeldebugging#227
The current PR adapts the MW test case to expect the step parameter to be displayed, as we should have expected in the first place.
Companion Pull Requests
(Warning: I forgot to give the same name to both branches)