Collectible Card Game Headquarters

Does anyone have a preference of using JUnit 3 over JUnit 4? I have to update the project's preferences to use one or the other.

Welcome!
I've never used either, so it's fine for me either way. 4 I guess (since it's newer, and maybe better?).

What is it and what did we use it for previously?

Rob Cashwalker wrote:What is it and what did we use it for previously?

Java's standard Unit Testing, and we didn't use it at all before.

Braids, I'm sure using 4 should be just fine.

thanks for the feed back. version 4 it is.

it turns out the correct answer to this question is neither. Dave (jendave) strongly prefers TestNG over JUnit. i believe that at present, the maven build freaks out when it encounters something that needs JUnit.

just another note about writing unit tests. some tests need to bootstrap most of the game in order to run. this includes constructing a { new CardFactory(ForgeProps.getFile(CARDSFOLDER)) } and calling { Gui_NewGame.loadDynamicGamedata() }. these operations can take a long time. on my least powerful computer, they take over 80 sec. during that time, it looks like TestNG is frozen. the problem is definitely not in TestNG, because i can run test/java/TinyTest.java very quickly.

Dave suggest that we need "mocks" and "dependency injectors" to make unit testing more feasible, and i agree. a mock is a simpler version of a class that that mimics some of its behaviors. a dependency injector is a means to tell the code to use a mock instead of the real thing. i suspect we'll be creating some alternative constructors for dependency injection; anything more fancy than that becomes difficult to understand.

earlier i was trying to avoid using a mock CardFactory by making CardFactory load its cards lazily. i will probably end up creating one that loads a few actual cards to avoid changing CardFactory.

anyway, this is the sort of thing i plan to be working on now. it will give me a better idea of how to set up the game state properly.