feat: Configure app termination via shouldTerminateApp capability #486
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
By default is true (as per the existing behaviour), which means the app gets terminated when the session gets killed, if a bundleId was specified.
mykola-mokhnach
approved these changes
Mar 24, 2021
|
What is the example usage scenario for this capability? As far as I remember the next session is anyway going to restart the app if launchApp XCTest API is called. |
|
ah yeah sorry i forgot to explain this in the description. the use case is for complex integration setups where the app lifetime is managed by third party tools, and other actions (outside the scope of the UI testing) must be taken after the test finishes and before the app can be killed. |
electricbubble
added a commit
to electricbubble/gwda
that referenced
this pull request
Mar 27, 2021
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.
By default is true (as per the existing behaviour), which means the app gets terminated when the session gets killed, if a bundleId was specified.