search

keplersj / BoatCraft

Rails had their turn, now out to the Minecraftian seas.
MIT License
6 stars 7 forks source link

Usefulness of unit testing #198

Closed viliml closed 10 years ago

viliml commented 10 years ago

I feel like we're just fixing tests because of the code, not the code because of the tests. If we could unit test the actual functionality of the boats in a started minecraft game, THEN it would make a bit of sense. This is silly! Do you have any arguments that support unit testing, other than the dirtchest9000 incident?

keplersj commented 10 years ago

Unit Tests will not be removed, their focus will simply be lessened. Soon here BoatCraft will be hard dependent on ForgeMicroBlock, from ForgeMultiPart, to get Materials from it's Registered Micro Material Array, ideally we should never have to define any more Materials or Material Crafting Recipes, which means in terms of content Unit Tests will will only ever have to test Modifiers, like Chests, and Core components.

viliml commented 10 years ago

Oh? Do tell!

viliml commented 10 years ago

I think you're going a little overboard with this... I mean, does it REALLY matter? I mean, we ALWAYS need to run the game and see if things work! This won't ever help anything!We basically do stuff, and then add some "safety" to make sure things are what they are, which they ARE! I don't care, I'm making a separate branch with unit testing! Feel free to merge other stuff in there whenever you want, but I don NOT want silly mistakes to mess up travis and stuff like that!

keplersj commented 10 years ago

I approve. This is definitely one of those good on paper situations.