Refactor and improve `GIDEMMSupport` parameters and tests
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- objective-c
- Domain
- authentication, mobile-dev, testing
Research direction
Start by reading the GIDEMMSupport implementation and its existing unit tests, especially parametersWithParameters and the tests that swizzle UIDevice. Check how the public API exposes this behavior and identify which tests rely on real device state. Done means nested-array key parameters are safely dropped, UIDevice mocking is consistent and hermetic, and coverage exercises the public API where appropriate.
Written by the indexing model from the issue text.
Description
This issue tracks follow-up improvements identified during the review of PR #608. We need to address the following technical debt and testing improvements:
- Handle nested data structures: Ensure that the
parametersWithParametersfunction safely drops key parameters that contain values like a nested array. - Standardize
UIDevicemocking: Fix the tests that are swizzlingUIDeviceto "Not Do That," or ensure all tests are doing it the same way. Relying on the realUIDevicewill make tests non-hermetic. - Uplevel tests to the public API: Consider upleveling the new
GIDEMMSupportunit tests to test against the public API instead of testing internal classes in isolation.
- Dominant language
- Objective-C
- Stars
- 751
- Forks
- 282
- Avg merge
- 4d 20h
- Merged PRs (30d)
- 11
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.
More from google/GoogleSignIn-iOS
-
enhancement triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
google/GoogleSignIn-iOS#621 ·
-
enhancement triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
google/GoogleSignIn-iOS#620 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
google/GoogleSignIn-iOS#440 · 4 comments · 2 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
google/GoogleSignIn-iOS#607 ·
-
enhancement triage
Difficulty 4/5 3-5 days Newbie friendliness 52/100
google/GoogleSignIn-iOS#602 ·
All issues in google/GoogleSignIn-iOS
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
objective-see/LuLu#925 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
noah-nuebling/mac-mouse-fix#2054 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
obsproject/obs-studio#13918 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HigherOrderCO/Bend#842 · 2 comments ·