Yeah, I think your best bet is the "hacked together" solution you described. I've done similar things for testing non-Buildr projects (ActiveObjects, my ORM, requires database access to run its test suite).
Daniel On Wed, Jul 29, 2009 at 2:41 PM, Shane Witbeck <[email protected]>wrote: > Daniel, > > Yes, the resources are specifically used for the unit and integration > tests. > They are primarily *.properties and *.xml files. I'm thinking that ideally > there should be a default set of test resources and then have the option to > override the resources path depending on which env the tests are being run > in. > > I guess this is an edge case which can be hacked together using profiles > and/or personal settings. Just curious what other people are doing. > > Thanks again, > > -Shane > > > On Wed, Jul 29, 2009 at 3:24 PM, Daniel Spiewak <[email protected]> > wrote: > > > > > > > 1. What's the best/standard? way of overriding the test resources and > > > have the tests work the same way in CI and development env's? > > > > > > I assume the resources you're talking about are used specifically by the > > unit tests? These should optimally be in src/test/resources/. However, > if > > these are external resources, then you should have a config file which is > > read by the tests to determine the relevant paths. > > > > 2. What's the best way of defaulting to running unit tests locally and > > > running unit and integration tests on the CI server? > > > > > > Sub-projects and integration testing: > > http://buildr.apache.org/projects.htmland > > http://buildr.apache.org/testing.html#integration At least, that's how > I > > assume it's supposed to work. I haven't used Buildr for integration > > testing, so my understanding could be a little flawed here. > > > > Daniel > > >
