On Wed, Oct 6, 2010 at 5:03 PM, Stanislav Muhametsin <[email protected]> wrote: > What is the policy for dev-status.xml contents about unit tests? Currently, > for example, in indexing-sql, it says that unit tests are none, however > there are 75 query-tests in appropriate project located in qi4j-tests. Do we > count strictly the tests in same project, or is some common sense allowed? I > would put that either to 'some' or 'good', since it passes through some > quite complex queries too.
That is an oversight from me, as I just put that file in. Feel free to adjust. The data is to be read by the www.qi4j.org website and show it in the component documentation, and overview page. The general policy that I want to see is; Err to the safe side. I.e. understate rather than overstate tests and documentation in place. Tests; none = none or so few that it is practically none some = covers all basic usecases good = covers all known usecases. complete = 100% (exception for untestable sections) test coverage of our own code. Documentation is less formalized, and use your own judgment, as what some people say is excellent documentation others would say is useless... Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
