Closed RenanLukas closed 3 weeks ago
1 Warning | |
---|---|
:warning: | Class Empty is missing tests, but unit-tests-exemption label was set to ignore this. |
Generated by :no_entry_sign: Danger
App Name | Jetpack | |
Flavor | Jalapeno | |
Build Type | Debug | |
Version | pr20695-101e25e | |
Commit | 101e25ed3929e349599ae19799cf80eb7cba3074 | |
Direct Download | jetpack-prototype-build-pr20695-101e25e.apk |
App Name | WordPress | |
Flavor | Jalapeno | |
Build Type | Debug | |
Version | pr20695-101e25e | |
Commit | 101e25ed3929e349599ae19799cf80eb7cba3074 | |
Direct Download | wordpress-prototype-build-pr20695-101e25e.apk |
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 82.58%. Comparing base (
1bab9d1
) to head (101e25e
). Report is 8 commits behind head on feature/tags-ia.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Fixes #20584
To Test:
The UI component is not being used yet, so in order to test it you can run
ReaderTagsFeedEmpty
preview and compare it with the existingDiscover
feed empty state: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):