Testsuite enhancements for validating affinity processing #378
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
|
@tadamski The codebase has been rebased. |
|
@rachmatowicz thanks. Just a small remark: could you please add license headers to added files. I have seen it is not present in AbstractEJBClientTestCase and Result classes. |
rachmatowicz
force-pushed
the
testsuite-enhancements
branch
from
2872d70
to
3dec524
Compare
Done |
tadamski
approved these changes
Mar 19, 2019
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.
This PR aims to add features to the EJB client testsuite in order to better validate affinity processing.
For details, see: https://issues.jboss.org/browse/EJBCLIENT-263
(NOTE: I had to recreate the pull request in GitHub due to changing the branch name). For reference, the old pull request was: #310)