zec
/
secant-android-wallet
mirror of https://github.com/zcash/secant-android-wallet.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
secant-android-wallet/docs/testing/manual_testing/Contact Support.md

2.0 KiB
Raw Blame History

Note: Contact Support will fail on some devices without an app to handle email, such as an Android TV device. See issue #386

Check Support Email Contents

  1. If using a test device or emulator, be sure to configure a default email app. For example, try opening the Gmail app and confirm that it shows your inbox.
  2. Clear the app's data. This ensures no crash reports exist on external storage
  3. Open the Zcash app
  4. Navigate to Profile
  5. Navigate to Support
  6. Type a message
  7. Choose send
  8. Choose OK
  9. Verify that the email app opens with a pre-filled message. The email subject should be "Zcash", the recipient should be the correct support email address, and the message body should include the message typed above, along with information about the user's current setup.

Verify Support Screen Closes After Send

  1. If using a test device or emulator, be sure to configure a default email app. For example, try opening the Gmail app and confirm that it shows your inbox.
  2. Open the Zcash app
  3. Navigate to Profile
  4. Navigate to Support
  5. Type a message
  6. Choose send
  7. Choose OK
  8. After the email app opens, task switch back to the Zcash app
  9. Verify that you're returned to the Profile screen (specifically confirm the Support screen with the confirmation dialog is no longer on the screen)

With Crashes

  1. If using a test device or emulator, be sure to configure a default email app. For example, try opening the Gmail app and confirm that it shows your inbox.
  2. Install a debug build of the app
  3. From the Home screen, choose Throw Uncaught Exception from the debug menu
  4. Repeat that at least 6 times
  5. Open the Zcash app
  6. Navigate to Profile
  7. Navigate to Support
  8. Type a message
  9. Choose send
  10. Choose OK
  11. Verify that the email app opens with a pre-filled message. Specifically look at the Exceptions section, verifying that it contains 5 entries (we limit to 5 to keep the email from getting too long). Note that the number of reported exceptions is set via CrashInfo.MAX_EXCEPTIONS_TO_REPORT and could be changed over time.