Headless Gui Tests#152
Merged
Merged
Conversation
Need to decide between these
Control run: pip install pytest-xvfb removed.
Contributor
Author
Collaborator
|
If you're renaming
|
Contributor
Author
|
Returned to normal |
This file contains hidden or 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
3 participants
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.
Changed the Github actions to account for XVFB usage. It seems easiest to use a combo of the GitHub action to download XVFB to our linux test and then use the pytest-xvfb plugin to have our tests auto use the installed XVFB. The tests I created are simple and only the top-level widgets were tested as they are the only windows and all subclass widgets will be tested. The tests will fail if an exemption occurs when generating the widgets. Should give us a baseline starting point. I couldn't directly test using XVFB so this may not work out of the box but base structure is there.