> -----Original Message----- > From: Alex Huang > Sent: Tuesday, February 05, 2013 2:23 PM > To: cloudstack-dev@incubator.apache.org > Cc: Edison Su > Subject: RE: [MERGE][ACS41] javelin to master > > > Alex, > > > > How about unit tests for the Javelin code itself? Were any created? > > Are there any that can be created? > > > > While the merge is already complete, this seems like a great time for > > the new structure to have unit tests built into it. > > > > There were no unit tests for the Spring DI and AOP given that Spring is an > established entity. > > There were unit tests and integration tests written for the storage refactor > portion using the Spring DI and AOP infrastructure. I'll let Edison speak to > what those are. 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.
> > --Alex
