Skip to content

Create an automated testing strategy #4

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
JakeWharton opened this issue Jul 9, 2015 · 1 comment · May be fixed by #7
Open

Create an automated testing strategy #4

JakeWharton opened this issue Jul 9, 2015 · 1 comment · May be fixed by #7

Comments

@JakeWharton
Copy link
Owner

Since this deals with process death an instrumentation-based test won't work. Maybe UI automator or UI automation could be used to drive the sample app. We can use the displayed process ID for asserting a new process is created. How do we assert against the activity stack, though?

At worst, a simple script which interacts over adb and dumps activity/process info and does text-based verification would work. But that's last resort.

@JakeWharton JakeWharton linked a pull request Jul 15, 2015 that will close this issue
@erikhuizinga
Copy link

Maybe the new Android Jetpack Navigation Architecture Component can help identify or enforce the activity stack?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants