Unit & Integration test investigation

[pmarsh-scottlogic]

Take stock of automated tests. See what bits of code we cover and which we don't. You could use test coverage tools for this, but to be more comprehensive, look at tests titles.

Write a list of functionality that has not been tested. Then prioritise in order of what's most used, what's most likely to go wrong, etc. Write tickets to implement.

AC: no code changes, therefore no testing needed.

[pmarsh-scottlogic]

would like to do this after #761

[pmarsh-scottlogic]

• chat controller unit tests missing tests for alerted but not triggered defences