When a new patch gets uploaded (and the tests run T62720) add a report for code coverage.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | None | T108737 Add code coverage report for Android app code | |||
| Resolved | • Niedzielski | T62720 Jenkins should run tests for the Wikipedia app before merge | |||
| Resolved | • bearND | T88494 Android app build: Gradle checkstyle + app build | |||
| Resolved | • Niedzielski | T103192 Request Jenkins shell access for account "sniedzielski" | |||
| Resolved | Dzahn | T103191 Request "wmf" group assignments for account "sniedzielski" | |||
| Resolved | hashar | T107336 Create jenkins slave instance dedicated to Android runs | |||
| Resolved | hashar | T110307 JJB support for Android Emulator plugin |
Event Timeline
Comment Actions
I had slightly mixed experiences with Android code coverage in the past. It really blew out the build time when instrumenting the code (note: cannot be the same artifact released) and I seem to recall the test code must be explicitly excluded when calculating coverage percentage. I think is a task worth striving for but the road might be a little bumpy.
Comment Actions
We now have a Jenkins job running from Gerrit and making use of the Android Emulator (was T62720). So I guess we can reuse what we learned there and generate a coverage report somehow.
Maybe on a daily basis? We have some reports being generated for other repositories under https://integration.wikimedia.org/cover/