This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
Add instrumentation tests for query rendered features #7127
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This PR contains a couple of tests that validate if query rendered features has regressed. It currently covers the 4 testapp activities related to query rendered features. The tests executes the default user action and validates if the expected result is shown in a Toast message/InfoWindow.
Related to f4b91fe, there is an issue on master that doesn't seem to load the map without moving it to xml, looking into this issue as part of #6532. update: the PR following #6532 is not showing this issue.
Review @ivovandongen