Skip to content
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

[Meta] - Support for deep link tests #2457

Open
5 tasks
matthew-carroll opened this issue Dec 18, 2024 · 1 comment
Open
5 tasks

[Meta] - Support for deep link tests #2457

matthew-carroll opened this issue Dec 18, 2024 · 1 comment
Labels
docs Concerns doc comments, READMEs, or docs

Comments

@matthew-carroll
Copy link

This is a meta ticket, which covers multiple related asks for deep link tests.

  • Documentation - Guide(s) for the current approach to testing deep links with Patrol
  • All lifecycles - Deep links can arrive at three different times. Each code path is different, and therefore each code path can have its own bugs. I'd like to test all three:
    • Cold boot (app is not in memory)
    • Background (app is in memory, but not executing code)
    • Foreground (app is visible on screen)

Deep links can be critical for business concerns. For example, a deep link might be used to get to a sign up page, or to a purchase page. Errors in such deep link handling can lead users to leave.

Moreover, deep links happen to be behaviors that aren't tested in the natural development process. Most developers don't even know how to simulate a deep link, let alone do it on a regular basis. Therefore, deep links are a perfect candidate for automated tests.

@Kendru98 Kendru98 added the docs Concerns doc comments, READMEs, or docs label Dec 19, 2024
@bartekpacia
Copy link
Contributor

Linking past discussion in #556

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Concerns doc comments, READMEs, or docs
Projects
None yet
Development

No branches or pull requests

3 participants