Tests

[Michael Terry <mike mterry name>]

Heyo!  Just an FYI about some more robust test procedures I'm putting in place.

I'm at UDS this week and Canonical has been talking about new
acceptance criteria for package updates landing in main and testing
requirements for projects they write.  This is going to affect the
upstream work I do on deja-dup, since I do that on company time now.

Basically the idea is that there has to be a growing body of automated
tests and a code review process.  Which are good ideas; they just
require a bit of work to get from A to B.

I've added some information to the wiki about code reviews [1].  Since
it's currently a development team of one, Canonical is letting Ken
VanDine (of Gwibber fame) spend time reviewing branches.  This way,
he'll also get up to speed on the code base so if I get hit by a bus,
maybe someone else can handle the code.

We already have tests, though they were rather wonky until recently
due to ldtp and gtk3 incompatibilities.  I'm going to clean them up
and add some unit tests to complement the existing integration tests.
Canonical has also agreed to run a Jenkins [2] instance to run tests
after every commit to trunk.  (This is not set up yet.)

[1] https://live.gnome.org/DejaDup/Policies#Code_Reviews
[2] http://jenkins-ci.org/

-mt