-
Notifications
You must be signed in to change notification settings - Fork 17
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
Code Testing #43
Comments
But the |
I agree that slider could use some unit tests, and probably integration/regression tests around the PP calculation and replay parsing. I haven't had time to do that, but I would be open to talking to you about setting that up if you are interested. |
I've been pretty busy recently but I should have a bunch of free time starting saturday so I can at the very least review code and probably write some too :) |
I propose to use the default unittest module and test out basic parts of the API. |
Given that we won't have much complicated persistent state to manage across tests, it's probably easier to use pytest. We use a mix of nose and pytest at work, and I have a slight preference for it. |
NOTE: an old map that has a linear type slider that we once failed to handle correctly, instead treating it like bezier: https://osu.ppy.sh/beatmapsets/19789#osu/69405 |
While we're at it why not test this QA gem from Zallius: "安心感" Another one: https://osu.ppy.sh/beatmapsets/104#osu/228 Minor plug: I've collected a table of pretty much every map loved/ranked up to August 2018 https://github.com/jxu/osu-stats/releases |
So I am not familiar with pytest or really "good practice" for testing (most testing I write is informal) I imagine the tests to be something like this:
For now I'm not sure if it needs to be more complicated than this. |
Unit tests at the very least to ensure updating the code doesn't break everything
The text was updated successfully, but these errors were encountered: