google/earlgrey

:tea: iOS UI Automation Test Framework

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 9 minutes ago
Added to GitGenius on September 11th, 2026
Created on February 4th, 2016
Open Issues & Pull Requests: 259 (+0)
GitHub issues: Enabled
Number of forks: 737
Total Stargazers: 5,693 (+0)
Total Subscribers: 224 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.6 days
Mean response time: 29.5 days
90th percentile: 189.1 days
Tracked items: 9

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 13
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 891 days
Stale 30+ days: 13
Stale 90+ days: 13

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • P2 (1)
  • type: bug (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

EarlGrey is a native iOS UI automation test framework that enables you to write clear, concise tests for iOS applications.

The framework addresses the challenge of flaky UI tests by providing enhanced synchronization features that automatically coordinate with the UI, network requests, and various queues before performing actions. This automatic synchronization ensures the UI reaches a steady state, which increases test stability and repeatability. The tool integrates with XCTest and Xcode's Test Navigator, allowing tests to run directly from Xcode or via command line using xcodebuild.

EarlGrey 1.0 is deprecated in favor of EarlGrey 2.0, which integrates with XCUITest. Developers should evaluate whether to adopt the newer version based on their iOS deployment targets and testing infrastructure. The framework suits teams building native iOS applications who need reliable UI automation testing with minimal flakiness. Those working with modern iOS versions should consider the EarlGrey 2.0 branch instead, as version 1.0 is not maintained for iOS 13 and later.

The project maintains documentation including features, backward compatibility notes, installation guides, and API references. Support resources include a FAQ, known issues documentation, and community channels on Stack Overflow and Google Groups.