search

EmergentOrganization / cell-rpg

:black_square_button: connect to a universe where cellular automata have run rampant
http://emergentorganization.github.io/bridge/
Other
12 stars 1 forks source link

organize tests #88

Closed 7yl4r closed 8 years ago

7yl4r commented 8 years ago

My current practice of putting tests into the same directory as the class being tested may not be optimal --- it certainly feels like I'm cluttering up the directory.

Answers to this stack overflow question generally seem to lean towards keeping production and testing code in separate root directories, i.e.:

src/core/src/com/emergentorganization/cellrpg/components/ExampleComponent.java
src/test/src/com/emergentorganization/cellrpg/components/ExampleComponentTest.java

I don't have any strong opinions on this issue, what does everyone else think?

BrianErikson commented 8 years ago

I agree with you there. At the rate we're going with Artemis, there's probably going to be three times more classes than normal, so separating the root dirs would be the cleanest way to do it

BrianErikson commented 8 years ago

Trello Ported