Lifecycle callbacks setupall investigation #1741
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
the
package: patrol
|
Remembering On iOS, this can simply be instrumentation's memory, because it lives for the whole duration of the test suite execution. On Android though, the instrumentation and app under test live in the same process, and both are killed and their memory is cleared after a single test finishes running. It's Android Test Orchestrator who manages execution, and it doesn't expose any APIs for storing some data persistently. Another idea is to store the status of As an example, we can take a look at how Allure accomplishes saving files to filesystem: |
|
Superseded by #1751. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Looks like it's not possible to for an instrumentation app to store cache/tmp files (link).