<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"> <html><body> <p>With github I know continuous integration is possible. On another project I work on we use it. The perk with travis is that it works with a YAML file plus when a PR is filed it send the patch to be built and lets you know in the PR if the build was successful or not. I am not sure though how that would fit into the workflow for you guys.</p> <p> </p> <div> <pre>--- Regards, Jonathan Aquilina Founder Eagle Eye T</pre> </div> <p>On 2014-09-11 17:29, Matthew Williams wrote:</p> <blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2px solid; margin-left:5px; width:100%"> <div dir="ltr">Hi Folks, <div> </div> <div>There seems to be a general push in the direction of having more mocking in unit tests. Obviously this is generally a good thing but there is still value in having integration tests that test a number of packages together. That's the subject of this mail - I'd like to start discussing how we want to do this. Some ideas to get the ball rolling:</div> <div> </div> <div>Having integration tests spread about the package and having environment variables that switch on/ off them being run</div> <div> </div> <div>$ JUJU_INTEGRATION go test ./...</div> <div> </div> <div>We could make use of build tags:</div> <div> </div> <div>$ go test -tags integration ./...</div> <div> </div> <div>We could put all the integration tests in a single package:</div> <div> </div> <div>$ go test <a href="http://github.com/juju/juju/integrationtests/.">github.com/juju/juju/integrationtests/.</a>..</div> <div> </div> <div> </div> <div>Thoughts?</div> <div> </div> <div>Matty</div> </div> </blockquote> </body></html>