From: Gerd M. <ge...@sm...> - 2001-08-30 10:39:02
|
Hi, > > I couldn't agree more! You should find that there is some test code in the > > CVS tree (src/com/techquila/topicmap/test) which is written using JUnit. But > > this test code is by no means exhaustive. > > > > I have been working recently on making that test code idependant of which > > back-end is in use (the memory package or the ozone one) and I don't think I > > have quite checked in all my changes yet. I'll have a look and check in > > anything that needs to be. > > > > If you would like to contribute test cases, then the only thing I would ask > > is that you write them using the JUnit framework (www.junit.org). > > > > Junit is also my favourite suite. Additional ant has a junit target that > makes it easy to include test running in the build process. > > Could we agree on these guidelines: > > - test code is part of the source tree (some tend to divide test code > completely) +1 > - test code for package are stored in packages parallel to the packages > to test with > an test suffix. package a.b.c would have a test package a.b.ctest. I would like to use the a.b.c.test variant. > - one additional package as a test suite base. this provides a package > for the main > test classes and for the classes which are wiring several test suites. We should have configurable testcases (I saw already an interface somewhere in TM4J for that). I've already written such a base test case for another project. The basic idea was to have a properties file and each testcase can access the properties of that file. > Is this ok? > > What about the package names of the API. Are there any plans to move the > package > naming from com.techquila to org.tm4j ? It isn't really important at the > moment but some things should be clear to everyone who is contributing code. > This includes the license thing. Best Regards, Gerd -- ________________________________________________________________ Gerd Mueller ge...@sm... SMB GmbH http://www.smb-tec.com |