On 11/9/06, Peter Kriens <[EMAIL PROTECTED]> wrote:
Yes, and I know that David agrees with that, and is not the point he tried to convey I think...
It is more about "setting it up". A unittest should be quick to write, refactor and execute.
Bingo.
I think everyone here agrees to the point that unit tests are unit tests, that can easily be kept outside the executing platform. And that we all use Junit for functional testing as well, and THAT is what this thread is really about.
I have previously been toying with the idea of using annotations in the test class to describe the test environment of the test, and then throw the class at a launcher, together with some "test time" arguments such as which OSGi platform to use.
You make it sound like the OSGi is a mighty beast like J2EE. Felix is
only about 250k and Knopflerfish is similar. Starting an OSGi
framework is very quickly in most cases and has less overhead than a
database.
Yes, and I know that David agrees with that, and is not the point he tried to convey I think...
I agree that unit testing should be just that.
Bingo.
I think everyone here agrees to the point that unit tests are unit tests, that can easily be kept outside the executing platform. And that we all use Junit for functional testing as well, and THAT is what this thread is really about.
However, I never got around to do something about it.
Cheers
Niclas
_______________________________________________ OSGi Developer Mail List osgi-dev@bundles.osgi.org http://bundles.osgi.org/mailman/listinfo/osgi-dev
