Before embarking on the refactor of MobileFrontend, we'd like to get a sense of how much code coverage we currently have inside the MobileFrontend codebase to show the value of this work. At the end of the project and at key points we'll observe how this has changed.
- Spike (4hrs) to check how feasible it is to run a one-off code coverage report for MobileFrontend.
- If feasible, measurement recorded inside https://www.mediawiki.org/wiki/Reading/Web/Projects/Invest_in_the_MobileFrontend_%26_MinervaNeue_frontend_architecture
- If it's not much extra work, commit the code coverage configuration. Otherwise, share it in an abandoned patch.
Note: There are very few unit tests in Minerva so we purposely exclude this from those measurements.