rust-windowing / rust-windowing/winit
Add more backends to the integration tests
Open
Nobody has claimed this yet.
DS - android
DS - appkit
DS - orbital
DS - uikit
DS - wayland
DS - web
DS - win32
- Dominant language
- Rust
- Stars
- 6.2k
- Forks
- 1.3k
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 9
Description
On the it branch, I've added an X11 backend that runs the tests in a Docker container. We should add other backends as well to match winit's backends.
- For Wayland, we can probably just add a headless Wayland compositor to the above Docker image.
- For Web, we can compile to WASM and run in a headless browser. (cc @daxpedda, you said you wanted to take a crack at this)
- For Windows, we can either run it in Wine under headless X11 or figure out if there is a way to do Windows heedlessly.
- For Android and iOS, we can use their simulators.
- Not sure about macOS, @madsmtm any ideas?
- Not sure about Orbital, @jackpot51 any ideas?
See https://github.com/rust-windowing/winit/issues/2866 for top-level issue about integration testing.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with dockerfiles/Dockerfile.ubuntu on the it branch and review the integration-testing setup referenced by issue #2866. Investigate how each proposed backend can run tests headlessly, including Wayland, Web/WASM, Windows, Android, iOS, macOS, and Orbital. Done means the relevant backends are covered by repeatable integration-test environments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, docker, ios, macos, rust, wasm
- Domain
- devops, infrastructure, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100