Add unittests #11

New issue

Closed

opened 2023-06-20 18:21:53 +02:00 by migration-script · 0 comments

migration-script commented

2023-06-20 18:21:53 +02:00

Summary

We should add unittests.

Description

As a developer, I want to be sure that the code is actually working as intended. Therefore we should add unittests. I suggest we use unit-threaded, because it is a major improvment over only using the builtin unittest blocks. Also it provides mocking functionality which we need for testing stuff that uses the database.

Acceptance criteria

If possible, functions should have unittests (stuff in calendarwebapp.calendarwebapp can not reasonably be tested and its probably also not usefull for the thin database wrappers). We should aim for a test coverage above 70%.

### Summary ### We should add unittests. ### Description ### As a developer, I want to be sure that the code is actually working as intended. Therefore we should add unittests. I suggest we use [unit-threaded](https://github.com/atilaneves/unit-threaded), because it is a major improvment over only using the builtin `unittest` blocks. Also it provides mocking functionality which we need for testing stuff that uses the database. ### Acceptance criteria ### If possible, functions should have unittests (stuff in `calendarwebapp.calendarwebapp` can not reasonably be tested and its probably also not usefull for the thin database wrappers). We should aim for a test coverage above 70%.