Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Add integration testing #2866

Open
notgull opened this issue Jun 9, 2023 · 2 comments
Open

Add integration testing #2866

notgull opened this issue Jun 9, 2023 · 2 comments

Comments

@notgull
Copy link
Member

notgull commented Jun 9, 2023

winit is for all intents and purposes tested either by hand or in prod. We should have integration tests run in CI to make sure that there aren't any regressions in our code, as well as to reduce the burden on maintainers to test the code.

The X11 backend can be tested using xvfb, and Windows generally doesn't have an issue with running heedlessly. Android can be tested using the Android virtual device that comes with the Linux image and iOS can be tested via the iOS simulator on the macOS image. Web should also be pretty easy to test with a headless browser. I'm not so sure about the other platforms.

@daxpedda
Copy link
Member

daxpedda commented Jun 9, 2023

I'm not sure what exactly is possible to simulate on other backends in CI, but for Web you can use WebDriver to basically do everything. I've used fantoccini with great success in the past.

I think it would be nice to potentially integrate stuff like that into winit-test?

@madsmtm
Copy link
Member

madsmtm commented Mar 28, 2024

Linking #3593 (comment):

for the purpose of integration tests, we should probably have some sort of mechanism to [run a closure shortly inside of the event loop] more easily.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Development

No branches or pull requests

4 participants