You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Writing unit tests for a game is no easy task, but fortunately some modules are pure and easy to test. In particular, the beatmap parser and the geometry module.
When playing the following beatmaps, I can't help but feel like the sound effects are… weird:
It's probably gonna be a tedious task, but I believe the best way to validate the hit parser would be to record an autoplay from the official osu! game and manually identify the played sound samples for the first dozens of hit objects. Then, write that using oshu!'s beatmap structure in a unit test, and check that the parser does interpret the correct thing.
Note that the parser module applies inheritance when parsing, so what appears in the resulting structure is ready to use by the game, and not exactly what's written in the beatmap file. Let's really focus on the expected result from the actual osu! game, rather than guess what the beatmap means.
The text was updated successfully, but these errors were encountered:
Writing unit tests for a game is no easy task, but fortunately some modules are pure and easy to test. In particular, the beatmap parser and the geometry module.
When playing the following beatmaps, I can't help but feel like the sound effects are… weird:
It's probably gonna be a tedious task, but I believe the best way to validate the hit parser would be to record an autoplay from the official osu! game and manually identify the played sound samples for the first dozens of hit objects. Then, write that using oshu!'s beatmap structure in a unit test, and check that the parser does interpret the correct thing.
Note that the parser module applies inheritance when parsing, so what appears in the resulting structure is ready to use by the game, and not exactly what's written in the beatmap file. Let's really focus on the expected result from the actual osu! game, rather than guess what the beatmap means.
The text was updated successfully, but these errors were encountered: