Adding EarlGrey to existing test suite causes black screen and failed assert
- Dominant language
- Objective-C
- Stars
- 5.7k
- Forks
- 737
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 5
Description
I have installed the EarlGrey framework using the Cocoapods method and added it to an existing suite of unit tests. Upon creating a new test and launching it, the app loads with a black screen and the test fails (as clearly there is nothing on the screen to test)
Is there additional setup required to add this to existing test suites? Are there settings that need modified?
Contributor guide
Research direction
Reproduce the failure in the existing iOS test suite after integrating EarlGrey through CocoaPods; start by checking the framework setup and test-target settings mentioned in the issue. Done means the test launches with a visible app screen and the assertion no longer fails.
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
- Needs clarification
- Newbie friendliness
- 25/100