Unit testing for core#3024
Merged
Merged
Conversation
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
1 participant
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 PR includes some of my AI-assisted explorations of how to unit/integration test core.
The motivation is simple. While our end-to-end tests at https://github.com/ammen99/wayfire-tests are very useful in catching bugs (and still have their place as a full-compositor test), the amount of tests there is growing rapidly. Given that each test needs a few seconds, this very quickly means that it is impractical to run all of the tests all of the time. By aiming for unit tests, we can hopefully have a much more comprehensive test suite, which also runs fast. For example, a simple xdg-shell test runs in 0.1s on my laptop.