On Tue, Dec 21, 2010 at 12:50 PM, Rickard Öberg <[email protected]> wrote:
> Hi guys,
>
> I'm adding some more features to Qi4j Core, and am finding it a bit awkward
> to add proper tests for it. Tests in general are quite spread out in
> qi4j-api,qi4j-spi,qi4j-runtime and then qi4j-tests/qi4j-tests-core. The main
> awkwardness I feel is the qi4j-tests-core, since it's in a totally separate
> repo.
>
> Could we move qi4j-tests-core into the core module, and then move all of the
> tests from qi4j-api,qi4j-spi,qi4j-runtime into qi4j-tests-core? That way
> qi4j-runtime does not need to have unnecessary and cyclic dependencies on
> e.g. test-support, and there would be one place to put tests.


In principle, I agree to some extent. I want the tests as close to the
classes under test as possible. Initially, the problem was the
sequence of dependencies between runtime and bootstrap (the latter
depended on the former), which is now gone. And I have been moving
tests from qi4j-tests repo to qi4j-core, but every here and there are
dependencies on libraries or even extensions, making those tests
nailed to a location after those repos are built.

So, feel free to move tests from qi4j-tests to qi4j-core if you can
find any more that are possible.

Further; qi4j-tests is in a mess by itself. So, I have for long been
thinking of changing the structure there a lot, regression/,
integration/ and performance/ comes to mind, where performance/ is not
a unit test suite, but something to execute as an application, i.e.
current cruft can effectively be removed for now.


Cheers
-- 
Niclas Hedhman, Software Developer
http://www.qi4j.org - New Energy for Java

I live here; http://tinyurl.com/3xugrbk
I work here; http://tinyurl.com/24svnvk
I relax here; http://tinyurl.com/2cgsug

_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev

Reply via email to