Closed jonasfj closed 1 year ago
dart test
has support for collecting code coverage:
https://pub.dev/packages/test#collecting-code-coverage
We should try this. Hopefully, it'll give us a percentage of how good our code coverage is.
We can use this to generate an HTML report, and that is useful for finding code that isn't covered by tests.
But we can also generate lcov files, and upload them to coveralls using: https://github.com/marketplace/actions/coveralls-github-action
I'm happy to help with the coveralls setup, if we can modify our github actions to output lcov files.
Obviously, follow up issues to computing coverage numbers is to write more tests to increase coverage numbers.
In hindsight this probably isn't a good first issue.
Let's try to compute some coverage numbers, maybe setup reporting to coveralls.