stadiamaps / stadiamaps/ferrostar
Plug any gaps in testing pre-1.0
Open
android
chore
core
iOS
- Dominant language
- Kotlin
- Stars
- 419
- Forks
- 81
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 7
Description
Probably mostly covered by #639, but adding a separate task here just in case before 1.0.
Maybe we can also try to add some "full launch" + automation tests (search for a place, get a route, start nav)?
Contributor guide
Research direction
Start by reviewing issue #639 and the repository's existing test setup to identify which pre-1.0 gaps remain. Define coverage for the proposed full-launch flow—search for a place, get a route, and start navigation—and consider the work done when those scenarios and relevant automation tests are covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile-dev, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100