Discussion: Error handling and testing

[Snorre98]

For now this should focus on the recruitment system, but this is a discussion which will have consequences for Samf4 as a whole.

We need to figure out how to deal with error handling and testing of the recruitment system. As soon as there is a clear picture of how we want to deal with this there will be created specific issues. There might be more here which I have not thought of.

The focus is on recruitment system because we are trying to create a robust release for the coming ISFiT recruitment, 11. august. This must at least have equal features and functionality as Samf3, but should have some new features. See #682.

Testing

We are doing some testing, specifically in the backend, but we need to get an overview of the extent of current testing. We should also make sure to implement Cypress tests in the frontend.

Error handling

We need to discuss how we want to deal with multiple types of error handling. For one it has to be considered if there should be a more consistent error response in the UI (Spinner, Toast and maybe error-induced 'Encountered Issue form' etc.). Secondly we should discuss to what extent we want error/anomaly logging, of course we need some logging. Do we want a similar system to what is implemented on Samf3 (automated e-mail on error), or some other solution.

Checks

• Map extent of backend testing

• Discuss frontend testing

• Come to a solution for uniformity in UI error response.

• Consider error logging and subsequent notification