1

 Whats EarlGrey?
 Why EarlGrey?
 Questions around EarlGrey?

2
 Native iOS testing framework.
 Developed by Google.
 Framework in Objective C but flexible
with swift as well.
 Possibility to write custom matchers.
 Page Object Model.
 EarlGrey users:

3
 Criteria EarlGrey

Unit Testing
✅ ❌
UI Testing
✅ ✅
Parallel Execution
✅ ❌
Support newer iOS
✅ ❌

4
 Criteria EarlGrey KIF

Syncronisation Automatic Wait statements Wait statements

Speed Fast Fastest Faster

Custom Matchers Can be written Needs to create a git Needs to create a

issue ticket.

5
 EarlGrey can be set to any iOS APP for an unit test target using POD or Carthage
files.
 For POD installation in the pod file the following code should be added in the pod
file:
target ‘targetName' do
pod 'EarlGrey', '= 1.15’
end
 For installation by carthage the following line should be added in the cart file:
github "google/EarlGrey" "1.15.0"

6
 Test engineers understand the dev code base better.
 The test execution time is less.
 Allows automatic synchronization.
 Debug the root cause analysis of the issue/ defect.

7
 What needs to be present in the iOS App or from the developer for the set up with
EarlGrey?
Following things would be needed for the setup:
- Dev code base as the framework is grey box testing.
- Accessibility Identifiers for the UI elements which would be under test.

8
 Where you can get the support for EarlGrey?
Google have their GitHub account (http://bit.ly/2H3wvKs) for EarlGrey related
issues. Google have a slack channel where people can’t post their queries and get
the resolution on EarlGrey.

 How and where do you write custom matchers?

EarlGrey provides a flexibility of writing functionalities used for various App
specific parts which are not included as part of the framework. The custom matchers
are conditional wait statement, getting text value from a label.

9
 What skillset needed for the person to start automation with EarlGrey as
framework?
Skillset or the knowledge required are:
- Basic knowledge of swift as programming language.
- EarlGrey framework knowledge, which would help to write custom matchers,
making changes in the framework for increasing the time to make the app specific
sync.

10
11
 There are alternatives to Appium.
 KIF/XCUITest can be good for static apps.
 EarlGrey handles both dynamic and heavy apps.
 Optimized solution would consider EarlGrey.

12
 EarlGrey github portal : http://bit.ly/2H3wvKs
 EarlGrey vs KIF—Testing framework – By Rodrigo Cavalcante:
http://bit.ly/2PLHbQA
 Cocoapods: https://cocoapods.org/
 Carthage: https://github.com/Carthage

13
14