Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Support for private tests #251

Open
Saviq opened this issue Nov 21, 2022 · 3 comments
Open

Support for private tests #251

Saviq opened this issue Nov 21, 2022 · 3 comments

Comments

@Saviq
Copy link
Collaborator

Saviq commented Nov 21, 2022

It would be nice to be able to support compositor-private tests.

Plausible soluition would be to allow injecting external test suites.

@i509VCB
Copy link

i509VCB commented Feb 22, 2023

It would be neat if this could also allow compositor private tests in another language (possibly Rust for smithay).

@bwidawsk
Copy link

bwidawsk commented Jan 9, 2024

Has any work progressed here since the original bug was filed? We're considering using WLCS in Chrome, and this would be a mandatory prerequisite.

If there are ideas on proof of concepts, I can consider trying to implement those.

@AlanGriffiths
Copy link
Contributor

No, I don't think anyone has had the motivation.

It would probably be easiest to fork the project and automate rebasing when there's a tag upstream.

To do it at runtime, I guess the trick would be an option to load a "private tests" shared library that contains googletest fixtures. (I'm not sure what is needed to ensure they register in the right place, but it ought to be possible.)

To write useful tests would require linking against some of the wlcs code and require some restructuring of the project including publishing headers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants