Skip to content

Write on-device integration tests for Android notifications #758

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
gnprice opened this issue Jun 20, 2024 · 0 comments
Open

Write on-device integration tests for Android notifications #758

gnprice opened this issue Jun 20, 2024 · 0 comments
Labels
a-Android Issues specific to Android, or requiring Android-specific work a-notifications a-tests

Comments

@gnprice
Copy link
Member

gnprice commented Jun 20, 2024

This is part of #757. As discussed in that issue, Android notifications are one of the few areas where we ought to have integration tests running on real devices, and are probably the top priority among those areas.

A prime example of this was #755, where it turned out that Android 11 and older (but not Android 12+) had a quirk that caused empty summary notifications to stick around after the notifications they contain were removed, unless the seemingly-irrelevant autoCancel flag was set (by calling setAutoCancel(true)). @rajveermalviya found that through patient manual testing; it would have been great to be able to find it through an automated test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a-Android Issues specific to Android, or requiring Android-specific work a-notifications a-tests
Projects
Status: No status
Development

No branches or pull requests

1 participant