Closed antonis closed 1 week ago
App Name | Jetpack | |
Flavor | Jalapeno | |
Build Type | Debug | |
Version | pr20715-9b612b3 | |
Commit | 9b612b39b0c4df34b1a22a54f31f8f86aab7d1e4 | |
Direct Download | jetpack-prototype-build-pr20715-9b612b3.apk |
App Name | WordPress | |
Flavor | Jalapeno | |
Build Type | Debug | |
Version | pr20715-9b612b3 | |
Commit | 9b612b39b0c4df34b1a22a54f31f8f86aab7d1e4 | |
Direct Download | wordpress-prototype-build-pr20715-9b612b3.apk |
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 40.70%. Comparing base (
8548a93
) to head (9b612b3
).
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code
This PR covers just item 1 of https://github.com/Automattic/wordpress-mobile/issues/23 and introduces a new mechanism for identifying achievement/milestone notifications (ref p1714062709630809/1714052620.609979-slack-C06BWNSR02K). The rest of the items will be covered in follow up PRs after refactoring part of the code.
To Test:
Regression Notes
Potential unintended areas of impact
What I did to test those areas of impact (or what existing automated tests I relied on)
What automated tests I added (or what prevented me from doing so)
PR Submission Checklist:
RELEASE-NOTES.txt
if necessary.Testing Checklist (strike-out the not-applying and unnecessary ones):