Unit test for the Input system #144
Open
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
ciro-unity
added
the
on hold
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Do you have a forum thread linked to this PR?
https://forum.unity.com/threads/what-about-unit-testing.981069/#post-6488173
What will this PR bring to the project for everyone?
Some example of a unit test for the input system and project structure for future tests. inlcudes tests for the input reader and unity's new input system.
Why are these changes necessary?
RE forum: the earlier we get this stuff in the easier it will be to maintain. Less headaches in the future =)
How did you implement them?
Mostly similar to #88 but with functional inputreader tests and no introduced packages/dependencies.