mapbox / mapbox/mapbox-navigation-android
Multiwaypoints using Core and UI SDK
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 651
- Forks
- 321
- PR merge metrics
- No merged PRs in 30d
Description
We need to verify the behavior of the Core and UI SDK `NavigationView` if a user sets multi waypoints and tries to navigate.
Test Cases to be covered:
Using Core SDK
- [x] Take a set of 25 waypoints(waypoints should be far from each other maybe like 1 km or more) and navigate
- [x] Take a set of 25 waypoints(waypoints should be close to each other i.e. the distance should not be more than ~50m b/w the waypoints) and navigate - We are waiting on ANS to give us the route they are following
- [ ] Take a set of 25 waypoints(waypoints should be close to each other i.e. the distance should not be more than ~50m b/w the waypoints) and navigate. Make sure this time you reroute sometimes. We cannot do this using the mock location app. Hence we need the history files. - See [this](https://github.com/mapbox/mapbox-navigation-android/issues/3298#issuecomment-656260459) for the history file attached.
If the above test cases succeed repeat them using `NavigationView`. If not, then we can confirm it's an issue in NavNative and we can close this ticket.
cc @asinghal22 @cafesilencio @zugaldia
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Core SDK and UI SDK NavigationView multiwaypoint scenarios described in the issue, including the history file linked from issue 3298. Run the 25-waypoint cases with close and distant points, including rerouting, then repeat them with NavigationView. Done means the cases succeed or the behavior is confirmed as a NavNative issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile-dev, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100