Fix swing tests #365
Merged
Fix swing tests #365
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
This also reverts commit 203dd49.
|
Note: I had to update JUnit for Utiliti to get SwingTestSuite to work with it. |
nightm4re94
approved these changes
Jan 3, 2021
Closed
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 pull request fixes a threading issue in the testing environment, which was discovered in #362.
It is unsafe to perform operations on swing components outside of the event dispatcher thread. Junit by default completes tests on a thread which is not the event dispatch thread.
I've created
SwingTestSuite.class, which is a test suite that executes all tests in the event dispatcher thread.Any class in the testing environment which performs operations on swing components should be annotated with
@ExtendWith(SwingTestSuite.class)so the tests will be executed in the swing test suite.