How to handle robot tests that need state

From !103 (merged)

How should we deal with robot tests which require specific database state?

With this change the handover test requires a user with a contact method which is a large amount of setup to do within the test itself.