Edison, You should enable the integration test suites. It shouldn't run in the normal mvn install but people should be able to run it with a different profile.
The goal of the integration has to be testing DataStoreProvider implementation without cloudstack at all. That's how you can know the DataStoreProvider implementation is completely decoupled from CloudStack. After doing this test, the DataStoreProvider implementer should have some assurance that CloudStack will run (even if it is in a deprecated form if there are bugs) with that implementation added to the plugins. --Alex > -----Original Message----- > From: Chip Childers [mailto:chip.child...@sungard.com] > Sent: Wednesday, February 06, 2013 11:12 AM > To: Edison Su > Cc: Alex Huang; cloudstack-dev@incubator.apache.org > Subject: Re: [MERGE][ACS41] javelin to master > > On Wed, Feb 06, 2013 at 10:45:32AM -0800, Edison Su wrote: > > There are unit test and integration test cases for storage components are > using Spring and TestNG. > > For example, there is a maven project called, *storage-integration-test*, > which can conduct integration test with storage engine, storage plugins, and > hypervisor resource. The integration test is written for devcloud > environment, so it's been disabled in the maven build. > > Regarding to unit test, , there are unit test cases under each storage > component, for newly created classes, but not for all of them. Before I > merge storage_refactor branch into master, I'll add more unit tests for these > newly created classes. > > > > Great news, thanks Edison!
