Project adaptation to work with external instrumentation runners #2
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
dpastor
changed the title
dpastor
changed the title
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.
🥅 What's the goal?
Until project is running during some time in some of our repos, i'm keeping it private, uploading artifacts to our private nexus.
Also some adaptations to the previous code are needed to give support to acceptance tests executions which are performed by external runners (composer in smart-wifi or marathon in android-messenger).
🚧 How do we do it?
loggerazziBefore...andlogerazziAfter...), which can be invoked manually on projects where android tests are run by an external runner (composer, marathon). See example on how this can be easily configured.📘 Documentation changes?
✅ How can I test this?