linkedin / linkedin/LayoutTest-iOS
Investigate why everything returns false for hasAmbiguousLayout
Open
Nobody has claimed this yet.
unit tests
- Dominant language
- Objective-C
- Stars
- 558
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Description
See UnitTestViews.m
For unit testing, the test has yet to come up with a view which actually has ambiguous layout according to the OS. It always seems to return true.
Maybe looking up some examples from WWDC videos would give some good examples.
Contributor guide
No contributing guide indexed for this repository
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
The issue points to UnitTestViews.m; start by reviewing its existing layout tests and the hasAmbiguousLayout result, then compare with ambiguous-layout examples from WWDC. Done means a test view reliably produces the intended OS result instead of always returning the same value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, objective-c
- Domain
- mobile, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100