we added a lot of new view function code to the backend section but there is a big problem. These functions are not tested enough and we have to deal with new bugs all the time. The best way to prevent this is to write unittests and make sure these unittests work when there is a new update. It may seem tedious at first, but you can't imagine how much easier it will be once it's written. For this, I need a team that is strong and has no job in life. Lets write unittests for
[x] user_views
[x] question_views
[x] comment_views
[ ] utilization_views
Note: For now since the newest branches are web-profile and 278-mutti-add-even-more-functions. We need to start our branches from here.
we added a lot of new view function code to the backend section but there is a big problem. These functions are not tested enough and we have to deal with new bugs all the time. The best way to prevent this is to write unittests and make sure these unittests work when there is a new update. It may seem tedious at first, but you can't imagine how much easier it will be once it's written. For this, I need a team that is strong and has no job in life. Lets write unittests for
Note: For now since the newest branches are web-profile and 278-mutti-add-even-more-functions. We need to start our branches from here.
Deadline: 20.11.2024 Estimated effort: 6 hrs Reviewer: @kristinatrajkovski @FatihAkgoz