ansaurus

Question

Answer 1

+3 A:

Tests are part of the product but only used by your company. You should check them in and version control them.

I suggest the first option as then the tests as seen as part of project A and not as something separate.

Also by checking them in, if other access this code, then they get to see it and thus you get them looking at tests, even if they never write any, they can use them to verify that the stuff they've done hasn't broken anything. If anything this is the most important reason for having the tests.

Preet Sangha 2010-09-28 08:42:59

Indeed, when you're not sure about wether you should use A or B, consider what you want to branch/tag atomically. You need to be able to branch your unit tests together with your actual code, so the first option is the only right one.

Sander Rijken 2010-09-28 08:46:59

Well, I get the points, and already thought of most of them before writing, but being in an environment where most people ignore unit tests, or don't even know what they are, and in a project where backwards compatibility is always present, and branches are rarely made, I find some arguments against them, ie: unit tests are surely just ran by me (or the CI server), and added by me, new tests are rarely added, and therefore, there will be less needs of making tests tags than main project ones. But I guess you are right and A is the way to go.

Neverbirth 2010-09-28 16:24:48

ansaurus

tags:

views:

answers:

Where to store the unit test classes?

related questions