> I would definitely go with Pax Exam for integration tests and JUnit for unit > tests.
Never used it, but looks good so let's give it a try! I am curious to see a comprehensive example in action ;) > Next step would be to add support for measuring code coverage. Was just looking into the build and added cobertura (not committed). Will that work with Pax Exam? Cause we def need coverage. grz Bram ________________________________________ From: amdatu-developers-bounces at amdatu.org [amdatu-developers-bounces at amdatu.org] On Behalf Of Marcel Offermans [[email protected]] Sent: Friday, October 08, 2010 11:08 PM To: amdatu-developers at amdatu.org Subject: Re: [Amdatu-developers] Unit/integration test On 8 Oct 2010, at 17:22 , Ivo Ladage-van Doorn wrote: Currently there are only a few (integration) tests, but no explicit choice for some test framework was made yet. After discussion with Angelo, we would like to propose using Pax Exam as testing framework. Pax Exam provides an easy way to run regular JUnit tests in a test OSGi container and they can be bound to the Maven lifecycle (test phase). Pax Exam is used for example by the Felix dependency manager. Feedback welcome. I would definitely go with Pax Exam for integration tests and JUnit for unit tests. Next step would be to add support for measuring code coverage. In the long run, we might want to reconsider the way we do tests, as a dynamic, component based system really needs a different mechanism for doing tests instead of doing them statically during some automated build process. I'm thinking of a way to deploy and run tests in a running framework, so you can deploy tests that relate to the set of components that you deployed, and you can continuously keep running tests to ensure the system is functioning correctly throughout its life time. Greetings, Marcel
