Our components are now Spring components.  They run within the Spring container, but our tests do not initialise a Spring container.

This is easily fixed by adding @SpringBootTest to the class.

However, this now means that we're starting a full Spring container before running our tests so they are going to be slower than standard JUnit tests.

We also have to consider that our H2 database is now used for the tests and that it is likely that the tests data will be updated by many people in the team over time.  That could make our tests fragile.  For example, if someone adds another charity - our current test will fail.  We may want to consider ways of fixing this.