That is amazing and awesome. Thanks, Martin and everyone else who helped with this! Lowering the barrier of entry to writing CI tests can only be a good thing.
On Thu, Dec 17, 2015 at 1:00 PM Martin Packman <martin.pack...@canonical.com> wrote: > I just added a cheaty way of getting started on a new CI test. > > $ make new-assess name=new_feature > > With 'new_feature' as the name you want for your test. This generates > a new test script, and some unit tests to go along with it, which you > can run as normal with: > > $ make test p=*new_feature* > > The QA team has done a fair bit of work of late both simplifying code > and updating older scripts. These templates should prove to be a > better example than looking at other random tests as we continue to > refactor things however. Input from our (many) python experts is > welcome. > > Next steps, a test runner that handles both environment setup and > annoying problems like ssh config neatly. > > Martin > > -- > Juju-dev mailing list > Juju-dev@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev >
-- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
