-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FUND] Add tests and significantly improve test coverage #781
Open
Labels
⭐ development fund 2022
A candidate for the Kitodo e.V. development fund.
💰 funded
A feature funded by the Kitodo e.V. development fund.
🛠 maintenance
A task to keep the code up-to-date and manageable.
Milestone
Comments
Priority 1
Priority 2
Priority 3
|
This was
linked to
pull requests
Feb 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
⭐ development fund 2022
A candidate for the Kitodo e.V. development fund.
💰 funded
A feature funded by the Kitodo e.V. development fund.
🛠 maintenance
A task to keep the code up-to-date and manageable.
Description
Currently Kitodo.Presentation barely has any (unit) tests, so implementing new features and making sure that nothing broke is very tedious and time consuming - not only for developers but for the release management as well. This proposal suggests to write a lot of tests and significantly improve test coverage for Kitodo.Presentation.
Related Issues
None.
Expected Benefits of this Development
Test-driven development ensures that developing new features, updating components or re-factoring code doesn't break anything (or at least makes obvious what broke). This is especially important for older projects with a large and complex code base, since it's impossible for a single developer to know every constraint and dependency.
Having tests would therefor improve code quality, make development easier and help testing and reviewing pull requests for the release management.
Estimated Costs and Complexity
Writing tests is not a complex, but a rather time-consuming task, so I'd estimate this to be of high cost and low complexity.
The text was updated successfully, but these errors were encountered: