[FIX] Improve some emulator and gradle parameters #4690
Merged
+16
−2
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.
The update test executed in GitHub actions has some flaky executions. In order to make it more robust and deterministic, some changes were done in the workflow:
-no-snapshotto the emulator options: That options will assure that no leftovers from other executions affect to the current one. It will work together with theforce-avd-creationparameter.autoforonin the-accelparameter: if hardware acceleration is available, it will be used making the test more robust. If not available, test will fail. GitHub actions' runners have the option available, so, we can assume that "con"--no-daemontogradlewcommand. That should not affect because there is only onegradlewcommand, but in the local executions could make the execution more performant.In addition, added
dependabot/*to theon:section, so the test will be executed in PRs opened by dependabot.Related Issues
App:
ReleaseNotesViewModel.ktcreating a newReleaseNote()with String resources (if required)QA