-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Create Audio Cue TestRail cases for Applause QA #36863
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
Comments
Nice, thanks for creating! Let me know what I can do to help. |
This issue has not been updated in over 15 days. eroding to Monthly issue. P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do! |
This issue has not been updated in over 15 days. eroding to Monthly issue. P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do! |
I will still do this, but don't have time yet |
Suggested test cases: 1) Chat notifications
2) Mention notifications
3) [Android/iOS] Notificiation sound should not stop device audio
|
We probably want to add a case for the Success sound, which happens when you complete a task or complete a payment, right? And maybe we need to add some guidance about when the user has "Mute all sounds from Expensify" enabled? |
4) Play 'Success' sound when user completes a payment or task
5) Sounds should be heard when user is reading current chat
6) Test mute sounds option
|
For 5, I think if you are viewing a chat and someone sends you a message, you should hear the received sound. Same with the send sound. Thoughts? |
That sounds correct. We don't see the native notification but we do hear the sound 👍 |
In progress |
Test cases created: https://github.com/Expensify/Expensify/issues/399791 |
cc @abekkala @shawnborton
Problem
We're getting bug reports that aren't necessarily bugs. Also the expected audio cue requirements aren't clear or documented.
Solution
Lets create a list of new Testrail cases.
The text was updated successfully, but these errors were encountered: