Unit tests for ErrorController. Issue#257

[Soupaa]

Description

Unit tests have been written for 4/5 Error handling functions in ErrorController. The last unfinished unit test, which is for Error 404 has not been written, as the correct solution to solve this specific area cannot be identified within the given time constraint.

Therefore this pull request contains these unit tests:

1. Unit test for Error 401 Unauthorized
2. Unit test for Error 403 Forbidden
3. Unit test for Error 400 BadRequest
4. Unit test for Error UnknownError

Fixes #\ Part of Issue #257

Type of change

• [x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?

The four unit tests has been written with xUnit. Therefore this issue is mainly about testing the existing function within ErrorController file.

The testing was conducted with the xUnit "Run Test" and "Run All Tests" buttons.

Development Configuration

• Flutter version: 2.0.5
• Dart version: 2.12.3

Checklist:

• [x] My code follows the style guidelines of this project
• [x] I have performed a self-review of my own code
• [x] I have commented my code, particularly in hard-to-understand areas, if necessary
• [ ] I have made corresponding changes to the documentation, if necessary
• [x] My changes generate no new warnings
• [x] I have added tests that prove my fix is effective or that my feature works, if necessary
• [x] New and existing unit tests pass locally with my changes
• [ ] Any dependent changes have been merged and published in downstream modules
• [ ] I have Acceptance Tested this on an iOS device
• [ ] I have Acceptance Tested this on an Android device

[makelblack159]

kan vi få den fixed så den ikke failer integration test ?

[JonasStjerne]

kan vi få den fixed så den ikke failer integration test ?

Unit test burde ikke have noget med integration test at gøre. Der bliver kigget på integration test en del det her sprint ved jeg. Der sker en fejl i dem ved connection til database.