service

The tests are now working again, and we've added some new ones.  We've also split the tests and the test data scripts.

Things to think about:

when is the data setup?
what's the order of the tests?
what is needed for the tests to run?
which components are we testing or are we testing end-to-end?

Thinking about the tests also helps us reconsider our design and the full contracts between components. The POST API should return a 201 response code and a header Location for the new charity.  This emphasises that the components have different concerns.  The service cares about coordinating the creation of a new charity in the domain.  The controller trusts the service to do that and it's concern is abiding by the REST standards.  Given this separation, maybe we could test the controllers in a different (and faster) way?