Writing unittests with coverage for all of LibreOffice might appear a daunting and insurmountable task. Given the vastness of the codebase it makes sense to focus on the areas of the codebase that historically have been hit most by regressions and are not already covered well by unittests.
There is a list of those areas at:
This EasyHack is to write unittests providing good coverage for these hotspots first, which should have the best benefit over cost and is much more limited in scope.
The regression hotspots can be cross compared with their respective test coverage:
(backups and historical data at: http://dev-builds.libreoffice.org/lcov_reports/)
Migrating Whiteboard tags to Keywords: (easyHack, difficultyBeginner, skillCpp, topicQA)
JanI is default CC for Easy Hacks (Add Jan; remove LibreOffice Dev List from CC)
Jaskaran committed a patch related to this issue.
It has been pushed to "master":
tdf#70448, Test for SetFormula function
It will be available in 5.2.0.
The patch should be included in the daily builds available at
http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
Affected users are encouraged to test the fix and report feedback.
Not my scope
I will start working on this. I will try to add unit tests for one of the area in the list. If someone could tell me a more specific area that needs unit tests that would be appreciated.