capturing test code in CVS

[Arcin Bozkurt - Archie]

What is the best way to capture test code for a module?

The first idea that comes to mind, is to keep a directory under the
module named Test to keep the test code. But normally the developers and
testers are seperated division in a company and they don't care about
each others code. Why should both have access to each others code in one
package?

And tester, most of the time do not need the code but just the
executable or the library created by that module.

So, should I create another module just for testing? It looks like I
will have bunch of modules distributed all around the repository...

What is a clean and useful solution to this simple problem?

-Arcin