On 2010-12-21 20.04, Niclas Hedhman wrote:
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.
The problem is that while runtime has dependencies on API, SPI and
bootstrap, it does not have the testsupport classes. So, in effect it
feels like the right thing to do is to simply move the qi4j-tests-core
to qi4j-core module. That would solve all the dependency issues it seems.
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.
That sounds like a good idea!
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
