Question

Using TDD, I’m considering creating an (throw-away) empty project as Test-harness/container for each new class I create. So that it exists in a little private bubble.

When I have a dependency and need to get something else from the wider project then I have to do some work to add it into my clean project file and I’m forced into thinking about this dependency. Assuming my class has a single responsibility then I ought not to have to do this very much.

Another benefit is an almost instant compile / test / edit cycle.

Once I’m happy with the class, I can then add it to the main project/solution.

Has anyone done anything similar before or is this crazy?

Answer 1

I have not done this in general, create an empty project to test a new class, although it could happen if I don’t want to modify the current projects in my editor.

The advantages could be :

• sure not to modify the main project, or commit by accident
• dependencies are none, with certaintly

The drawbacks could be :

• cost some time …
• as soon as you want to add one dependency on your main project, you instantly get all the classes in that project … not what you want
• thinking about dependencies is usual, we normally don’t need an empty project to do so
• some tools check your project dependencies to verify they follow a set of rules, it could be better to use of those (as that could be used not only when starting a class, but also later on).
• the private bubble concept can also by found as import statements.
• current development environments on current machines already give you extra-fast operations … if not, you could do something about it (tell us more …)
• when ok, you would need to copy to your regular project your main and your test class. This can cost you time, especially as the package might not be adequate (simplest possible in your early case because your project is empty, but adequate to your regular project later).

Overall, I’m afraid this would not be a timesaver… 🙁