Yes, at least some of the ones I wrote. I guess these are more of integration / sanity tests. Even if the build server could get the schema installed prior to running these tests, some of the rows are populated only when the server is run. Some of these tests rely on these entries since they run after the configure() state in the lifecycle of the manager.
On 1/24/13 4:58 PM, "Alex Huang" <alex.hu...@citrix.com> wrote: >We just discovered that majority of the unit tests have been disabled due >to the build machine can't access the db. Is this correct? > >--Alex > >> -----Original Message----- >> From: Alex Huang [mailto:alex.hu...@citrix.com] >> Sent: Thursday, January 24, 2013 4:17 PM >> To: cloudstack-dev@incubator.apache.org >> Subject: Writing unit tests after javelin is merged in. >> >> I wrote up a page on how to write unit tests after the Spring injection >> framework is in. Please see here. >> >> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Unit+Testing+wi >> th+JUnit+and+Spring >> >> We also need help in javelin to finish converting the unit tests over >>to this >> format. If you can help, let me know. >> >> Thanks. >> >> --Alex >> >
