NavigationStack and TabView have inadequate automated testing
Open
Nobody has claimed this yet.
debugging
navigation
- Dominant language
- Swift
- Stars
- 330
- Forks
- 76
- Avg merge
- 3h 6m
- Merged PRs (30d)
- 1
Description
NavigationStack and TabView are incredibly complicated pieces of code; it's extremely difficult to touch them without accidentally breaking something.
skip-ui has some automated tests, but no automated tests of these areas. We should fix that, ideally not (merely) by adding automated tests to https://github.com/skiptools/skipapp-showcase but adding tests that run during the skip-ui CI.
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 locating the NavigationStack and TabView implementations and the existing skip-ui automated tests; then determine how tests are run in skip-ui CI. Done means these areas have automated coverage that runs during skip-ui CI, rather than only in skipapp-showcase.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- ci-cd, mobile, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100