Add some basic tests for easing functions #16675
Open
+64
−0
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.
Objective
Context for #16676
The release notes nerd-sniped me again. I was looking at the
EaseFunction::Exponential*
definition and wondering why that specific definition was chosen. And looking into it I noticed that it seemed wrong and there weren't any tests, so here are those tests -- which are failing as proof.Solution
I don't know what the best answer is here, but I think having tests is at least a good start for a discussion.
Testing
These are tests 🙂