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.

Sign up for GitHub

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

Jump to bottom

Document a test strategy for new snippets #162

Open

yschimke opened this issue Mar 8, 2023 · 1 comment

yschimke commented Mar 8, 2023

With this PR #158, there is a question "What are the breakages from bumping the targetSDK?"

It would be good to have a pattern for new snippets at least, to demonstrate that the snippet works on some particular device.

Useful when

changing the code of the snippet
changing the build such as targetSdk
testing against some new device

Author

yschimke commented Mar 8, 2023 •

edited

Loading

Question from @xpconanfan

How you would confirm the API actually behaved though?
It sounds like end to end or integration tests? Who would provide the HW to run those on?

run on emulator (GMD) to test or FTL devices?

GMD here https://android-developers.googleblog.com/2021/10/whats-new-in-scalable-automated-testing.html

Similar integration with FTL https://developer.android.com/studio/preview/features#ftl-gmd

As for what to test, I think that depends on the snippet, it might be enough to test against known state of the emulator.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment