Update docs and make them more lean #458

tirodkar · 2017-03-17T23:05:55Z

No description provided.

khandpur · 2017-03-18T00:31:37Z

docs/faq.md

@@ -18,9 +26,16 @@ assertions. The ability to search for elements (using search actions) makes test
 UI changes. For example, EarlGrey provides APIs that allow searching for elements in scrollable
 containers, regardless of the amount of scrolling required.

+**Why do tests have the video cropped? How can  I get them to fit in the video frame?**


IIRC it's not cropped. It's just scaled w/ borders around it. Plz double check?

khandpur · 2017-03-18T00:33:19Z

docs/faq.md

 **I get a crash with “Could not swizzle …”**

-This means that EarlGrey is trying to swizzle a method that it has swizzled before. It is a result of EarlGrey being linked to more than once. Ensure that only the **Test Target**
+This means that EarlGrey is trying to swizzle a method that it has swizzled before. It is a result
+of EarlGrey being linked to more than once. Ensure that only the **Test Target**
 depends on *EarlGrey.framework* and EarlGrey.framework is embedded in the app under test (i.e. *$TEST_HOST*) from the
 test target's build phase.


from the test target's build phase via Copy File(s) Script?

khandpur · 2017-03-18T00:44:41Z

docs/install-and-run.md


 ### CocoaPods installation

-For EarlGrey, we highly recommend [CocoaPods](https://cocoapods.org/) as the best way to get started.
+#### Step 1: Set up a Unit target      ///// EarlGrey adds changes to the test target's Scheme and Build Phases


Comment I forgot to erase. Thanks.

khandpur · 2017-03-18T00:50:08Z

docs/install-and-run.md


-      <img src="images/image00.png" width="500">
+Click Next → "Add a Test Target Name" → Finish.


make this bold like others? or keep em consistent. also what's special about "Add a Test Target Name". I don't think Xcode 8 has those screens.

It isn't a concrete button title but more of an action to be done. Made the step actions bold throughout.

khandpur · 2017-03-18T00:50:32Z

docs/install-and-run.md

-     `pod install` command. If your **Test Target(s)** do not contain these changes to the
-     [Scheme](#scheme-changes) and [Build Phases](#build-phase-changes) after running
-     `pod install`, please re-run `pod install` again.
+And clock on Close.


clock => click...make Close bold?

khandpur · 2017-03-18T00:53:10Z

docs/install-and-run.md

-  PROJECT_NAME = 'SampleApp'
-  TEST_TARGET = 'SampleAppTests'
-  SCHEME_FILE = 'SampleAppTests.xcscheme'
+```ruby


indentations seem to be removed

khandpur · 2017-03-18T00:55:16Z

docs/install-and-run.md

-     To download a particular version of the gem, use `gem install earlgrey -v x.y.z`.
+5. Install the EarlGrey gem by doing `gem install earlgrey` and then do the `pod install`.
+
+Notes:


Is it possible to highlight this like notes, maybe light blue or green section?

It doesn't seem like it's possible to add color to plaintext in Github markdown.

http://stackoverflow.com/questions/11509830/how-to-add-color-to-githubs-readme-md-file

khandpur · 2017-03-18T00:56:36Z

docs/install-and-run.md


-  2. As part of the initial build step, a script **setup-earlgrey.sh** will be run to download all the required dependencies. Without it, you might find dependencies like `fishhook` and `OCHamcrest` shown as missing in the folder structure.
+2. As part of the initial build step, a script **setup-earlgrey.sh** will be run to download all the


link to setup-earlgrey.sh

khandpur · 2017-03-18T00:58:41Z

docs/install-and-run.md

 #### Step 1: Set up a test target for Carthage

 See [Step 1 from the `CocoaPods installation`](#step-1-set-up-a-test-target) detailed above.

 #### Step 2: Configure carthage

-Install Carthage
+1. Install Carthage

 `brew update; brew install carthage`


instead of ` so that it looks like the code blocks above. The color of code block using ` seems slightly different from

I'd have to surround all in a ``` to get them to look the same. These are steps to be performed rather than code blocks, so I'd assume that should be fine. Do you think it would be better to turn these into code blocks?

khandpur · 2017-03-18T00:59:43Z

docs/install-and-run.md


 The EarlGrey tests are hosted from the application being tested. Make sure the test target is setup
 correctly to launch the app under test:

 1. Under the **General** tab:
-   * **Host Application** is set to the app under test.


this shows up as:

Under the General tab: a) Host Application is set to the app under test.

Please fix it here and for the other numbered bullets below

Adding a) etc. doesn't seem to indent this correctly. Just changed this to * everywhere.

bootstraponline · 2017-03-20T15:35:47Z

docs/faq.md

@@ -1,5 +1,13 @@
 # FAQ

+**I did a fresh `git clone` of the EarlGreyExample CocoaPods Demo project followed by a
+`pod install`. However, I get an error similar to `No such module 'EarlGrey'`.**
+This is a known issue with EarlGrey's CocoaPods support. EarlGrey requires some additions to the


you need an empty line after the bold text

**question** answer

bootstraponline · 2017-03-20T15:36:26Z

docs/faq.md

+test project's Build Settings and Schemes. If your **Test Target(s)** do not contain these changes
+to the [Scheme](./install-and-run.md#scheme-changes) and
+[Build Phases](./install-and-run.md#build-phase-changes) after running `pod install`, please re-run
+`pod install` again.'


again.' should have the ' removed.

bootstraponline · 2017-03-20T15:38:17Z

docs/faq.md

@@ -29,7 +46,7 @@ undefined.” in the logs**

 This usually means that EarlGrey is being linked to more than once. Ensure that only the **Test Target**
 depends on *EarlGrey.framework* and EarlGrey.framework is embedded in the app under test (i.e. *$TEST_HOST*) from the
-test target's build phase.
+test target's built products via a Copy File(s) script.


built products via a Copy File(s) script.

is not correct. Xcode refers to Build Phases

Changed to Copy Files(s) Build Phase

bootstraponline · 2017-03-20T15:39:23Z

docs/install-and-run.md

-You can add EarlGrey to Xcode projects in two ways: using CocoaPods, or as a framework. If you wish to contribute to the EarlGrey project, the **EarlGrey.xcodeproj** generated from the [GitHub Installation](#github-installation) section is integrated with the Unit and Functional Test projects for you to work with the source.
+You can add EarlGrey to Xcode projects in three ways: using CocoaPods, Carthage or manually through the Xcode Project.
+
+For EarlGrey, we highly recommend [CocoaPods](http://cocoapods.org/pods/EarLGrey) as the best way to get started.


Use https. Also the L should not be capitalized.

https://cocoapods.org/pods/EarlGrey

bootstraponline · 2017-03-20T15:41:16Z

docs/install-and-run.md

-     To download a particular version of the gem, use `gem install earlgrey -v x.y.z`.
+Notes:
+* Call the `configure_for_earlgrey` method for each target / Scheme.
+* For compatibility between different versions, please peruse [this doc](https://github.com/google/EarlGrey/tree/master/docs/versions.md).


please see [this doc] seems more natural.

I think we should start matching the gem versions with EG versions. Asking users to consult a compatability document isn't a great user experience.

We tried discussing this before. Won't going from 0.1.6 to 1.8 or so be odd?

I don't think so. Using 0.1.6 for EarlGrey 1.8 is a bit confusing. The gem is stable now, is there a reason to stay on 0.x.x?

Gem 1.8 for EarlGrey 1.8 seems like a natural fit.

Sounds fine. We're going to have to get them to parity sometime soon, though it would probably break semantic versioning for the gem. @khandpur WDYT?

I think moving to 1.x.x is in line with semver.

How do I know when to release 1.0.0?

If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0. If you’re worrying a lot about backwards compatibility, you should probably already be 1.0.0.

http://semver.org/

But to keep them in parity we're going to have to move them to 1.8.1 for the next release right? Will that be fine?

Yes, it will be fine. In general there's no deep meaning to the Ruby gem version numbers. In this specific case, I think version parity is more important than strictly following semver.

bootstraponline · 2017-03-20T15:42:34Z

docs/install-and-run.md

-  1. Download the source for EarlGrey and its dependencies.
-     * Download EarlGrey's source code from the [Latest Release](https://github.com/google/EarlGrey/archive/1.0.0.zip)
+1. Download the source for EarlGrey and its dependencies.
+  * Download EarlGrey's source code from the [Latest Release](https://github.com/google/EarlGrey/archive/1.0.0.zip)


1.0 is not the latest release. Use this link instead:

https://github.com/google/EarlGrey/releases/latest

Done. Thanks!

bootstraponline · 2017-03-20T15:43:25Z

docs/install-and-run.md


-     * Unzip and go to the `EarlGrey-1.0.0/EarlGrey` directory that contains **EarlGrey.xcodeproj**.
+  * Unzip and go to the `EarlGrey-1.0.0/EarlGrey` directory that contains **EarlGrey.xcodeproj**.


should probably make this version independent:

EarlGrey-x.y.z/EarlGrey

bootstraponline · 2017-03-20T15:44:55Z

docs/install-and-run.md

 ```

-> For compatibility with Swift, we use `grey_allOfMatchers()` and `grey_anyOfMatchers()` instead of `grey_allOf()`
-and `grey_anyOf()` respectively.
+> For compatibility with Swift 2.3, we use `grey_allOfMatchers()` and `grey_anyOfMatchers()`


is this no longer an issue on Swift 3? otherwise I don't think it makes sense to say 2.3.

We still use grey_allOfMatchers in Swift 3. Removed the 2.3 sicne it was a little confusing.

tirodkar · 2017-03-20T18:34:41Z

docs/faq.md

+launch screen images present for all supported devices (see 
+[iOS Developer Library, Launch Files](https://developer.apple.com/library/ios/documentation/UserExperience/Conceptual/MobileHIG/LaunchImages.html)).
+
+**Why does EarlGrey need to modify the test's scheme and add a Copy Files Build Phase?**


@khandpur PTAL. Added a question to address info for the scheme changes.

AVandelay · 2017-03-20T18:42:40Z

docs/install-and-run.md


 ### Carthage Installation

-EarlGrey supports Carthage via [the EarlGrey gem.](https://rubygems.org/gems/earlgrey)
-
 #### Step 1: Set up a test target for Carthage

 See [Step 1 from the `CocoaPods installation`](#step-1-set-up-a-test-target) detailed above.


Can this just be written out? Section 3 documents running pod install which shouldn't apply here

@AVandelay sorry, I'm a little confused here.

#### Step 1: Set up a Unit target doesn't mention pod install. Am I looking at something else?

sorry. I was comparing with the version currently published. Looks like this comment is irrelevant now.

khandpur · 2017-03-23T03:04:11Z

docs/install-and-run.md

 ## Install EarlGrey

-You can add EarlGrey to Xcode projects in two ways: using CocoaPods, or as a framework. If you wish to contribute to the EarlGrey project, the **EarlGrey.xcodeproj** generated from the [GitHub Installation](#github-installation) section is integrated with the Unit and Functional Test projects for you to work with the source.
+You can add EarlGrey to Xcode projects in three ways: using CocoaPods, Carthage or manually through the Xcode Project.


using CocoaPods, Carthage or manually

Can we add links for each so clicking on Cocoapods takes me directly to cocoapods installation instructions?

khandpur · 2017-03-23T03:04:57Z

docs/install-and-run.md


 ### CocoaPods installation

-For EarlGrey, we highly recommend [CocoaPods](https://cocoapods.org/) as the best way to get started.
+#### Step 1: Set up a Unit target


Unit => Unit test

khandpur · 2017-03-23T03:07:20Z

docs/install-and-run.md

-    configure_for_earlgrey(installer, PROJECT_NAME, TEST_TARGET, SCHEME_FILE) # EarlGrey Gem Call
-  end
-  ```
+4. Install the EarlGrey gem by doing `gem install earlgrey` and then do the `pod install`.


Move gem install out to first step.

Then in the step where user is asked to do configure_for_earlgrey, tell them they do it for each target / Scheme.

The very last step should be pod install along with this note:
For compatibility between different versions, please see this doc. To download a particular version of the gem, use gem install earlgrey -v x.y.z.

khandpur · 2017-03-23T03:12:59Z

docs/install-and-run.md

+Notes:
+* Call the `configure_for_earlgrey` method for each target / Scheme.
+* For compatibility between different versions, please see [this doc](https://github.com/google/EarlGrey/tree/master/docs/versions.md).
+To download a particular version of the gem, use `gem install earlgrey -v x.y.z`.

 #### Step 3: Run the pod install command


Rename this as you've already done pod install.

Step 3: Open workspace and verify that you see EarlGrey.

khandpur · 2017-03-23T03:14:00Z

docs/install-and-run.md

-  1. Download the source for EarlGrey and its dependencies.
-     * Download EarlGrey's source code from the [Latest Release](https://github.com/google/EarlGrey/archive/1.0.0.zip)
+1. Download the source for EarlGrey and its dependencies.
+  * Download EarlGrey's source code from the [Latest Release](https://github.com/google/EarlGrey/releases/latest)


Not intended correctly here and below.

Done. Changed the indentation throughout.

khandpur · 2017-03-23T03:27:28Z

docs/install-and-run.md

-1. Include the `EarlGrey.swift` file in your Swift Test Project. The file contains functions that
-   implement C preprocessor macros that aren't available in Swift.
+#### Using the [earlgrey gem](https://rubygems.org/gems/earlgrey): 
+* We recommend uisng the EarlGrey gem to use EarlGrey with Swift.


Remove this. It's inferred

khandpur · 2017-03-23T03:27:41Z

docs/install-and-run.md

- EarlGrey.select(elementWithMatcher: grey_accessibilityID("ClickMe"))
-   .assert(grey_sufficientlyVisible())
+// Select the button with Accessibility ID "clickMe" and assert it's visible.
+EarlGrey.select(elementWithMatcher: grey_accessibilityID("ClickMe"))


indentation

khandpur · 2017-03-23T03:28:09Z

docs/install-and-run.md

 ```

-> For compatibility with Swift, we use `grey_allOfMatchers()` and `grey_anyOfMatchers()` instead of `grey_allOf()`
-and `grey_anyOf()` respectively.
+> For compatibility with Swift, we use `grey_allOfMatchers()` and `grey_anyOfMatchers()` instead


Don't need this at all here.

khandpur · 2017-03-23T03:29:23Z

docs/install-and-run.md

-      EarlGrey currently supports Swift 3.0 and 2.3. While 3.0 is the default, you can also use 2.3 by adding
-      `{swift: true, swift_version: 2.3}`.
+EarlGrey currently supports Swift 3.0 and 2.3. While 3.0 is the default, you can also use 2.3
+by adding `{swift: true, swift_version: 2.3}`.


{swift: true, swift_version: 2.3} where? in Podfile?

Removed this altogether. Don't think it's needed and the gem docs provide any needed details.

khandpur · 2017-03-23T03:32:35Z

docs/install-and-run.md

@@ -263,40 +275,39 @@ your test and in your application code and use the built-in tools seamlessly.

 ### Swift


Get rid of this section and move it closer to where are integrating w/ gem and manual installation when they're integrating with EarlGrey. Makes them optional for swift only.

Done. Moved the needed sections to the installation steps.

khandpur · 2017-03-23T08:34:43Z

docs/faq.md

@@ -1,5 +1,14 @@
 # FAQ

+**I did a fresh `git clone` of the EarlGreyExample CocoaPods Demo project followed by a


Doesn't Hao's changes nullify this?

It most certainly will.

Kept it here for now for Hao to update it with the latest changes.

He plans on getting it in for the next release so lets remove this? we might forget to not remove it.

khandpur · 2017-03-23T08:37:51Z

docs/faq.md

+launch screen images present for all supported devices (see 
+[iOS Developer Library, Launch Files](https://developer.apple.com/library/ios/documentation/UserExperience/Conceptual/MobileHIG/LaunchImages.html)).
+
+**Why does EarlGrey need to modify the test's scheme and add a Copy Files Build Phase?**


Is this really one of the FAQ?

In general, we shouldn't add Q's to FAQ section unless they are actually asked frequently. For one-time questions SO is the better option.

Can we add this to ifaq.md for infrequently asked questions? This came up as part of the AWS eval. It'd be nice to have an official answer instead of sending people to SO or Google. Other iOS frameworks don't require this setup so I think it makes sense to explain why this is necessary.

Added an ifaq.md file with this question.

khandpur · 2017-03-23T08:39:24Z

docs/faq.md

@@ -29,7 +58,7 @@ undefined.” in the logs**

 This usually means that EarlGrey is being linked to more than once. Ensure that only the **Test Target**
 depends on *EarlGrey.framework* and EarlGrey.framework is embedded in the app under test (i.e. *$TEST_HOST*) from the
-test target's build phase.
+test target's built products via a Copy File(s) Build Phase.

 **Is there a way to return a specific element?**


This should be much higher, probably the 2nd from the top. If you're modifying FAQs anyways, I'd suggest look at the existing entries and re-order them based on popularity with highest on the top.

khandpur · 2017-03-28T07:27:18Z

docs/faq.md

+of EarlGrey being linked to more than once. Ensure that only the **Test Target**
+depends on *EarlGrey.framework* and EarlGrey.framework is embedded in the app under test (i.e. *$TEST_HOST*) from the
+test target's build phase.
+
 **How do I check whether an element exists in the UI hierarchy?**


Under How should I handle animations?, there's a code snippet that shows how to speed up animations:
UIApplication.sharedApplication().keyWindow?.layer.speed = 100

Could we change it to use the TestHelper instead?
https://github.com/google/EarlGrey/blob/master/EarlGrey/Common/GREYTestHelper.m

khandpur · 2017-03-28T07:28:23Z

docs/ifaq.md

@@ -0,0 +1,13 @@
+#IFAQ - Infrequently Asked Questions


This doesn't render correctly:

https://github.com/tirodkar/EarlGrey/blob/7e5b64c693082b26628d481a1b8e39232474b0f3/docs/ifaq.md

Also are you planning on linking this file to README or from somewhere in FAQ?

README. Adding it.

khandpur · 2017-03-28T07:30:34Z

docs/install-and-run.md

-## Prerequisites
-
-For EarlGrey to function properly, make sure the app under test has correct launch screen images present for all supported devices (see [iOS Developer Library, Launch Files](https://developer.apple.com/library/ios/documentation/UserExperience/Conceptual/MobileHIG/LaunchImages.html)).
+test.M


khandpur · 2017-03-28T07:31:34Z

docs/install-and-run.md


-### CocoaPods installation
+For EarlGrey, we highly recommend [CocoaPods](http://cocoapods.org/pods/EarlGrey) as the best way to get started.


The cocoapods link should point to the section inside this file for Cocoapods installation

khandpur · 2017-03-28T07:38:25Z

docs/install-and-run.md

+        configure_for_earlgrey(installer, PROJECT_NAME, TEST_TARGET, SCHEME_FILE) # EarlGrey Gem Call
+      end
+      ```
+      The EarlGrey gem also copies the `EarlGrey.swift` file to your project directory if you're passing the `{swift: true}` parameter to the args for the configure_for_earlgrey() method.


Show code example for swift users. Majority will be using swift.

khandpur · 2017-03-28T07:41:06Z

docs/install-and-run.md

-Now you're ready to start testing with EarlGrey!
-If you need more control, review the available install options.
+      Now you're ready to start testing with EarlGrey!
+      If you need more control, review the available installation options in the `earlgrey gem`:


why is earlgrey gem highlighted as code here?

khandpur · 2017-03-28T07:41:48Z

docs/install-and-run.md


-`earlgrey help install`
+      `earlgrey help install`

 ### GitHub Installation

 In cases where CocoaPods is not compatible with your project, you can add EarlGrey manually to your Xcode project.


Don't need to mention cocoapods not being compatible...Just say some like: if cocoapods or carthage don't work you then you can integrate manually.

"If CocoaPods or Carthage doesn't suit your use case, then you can add EarlGrey manually to your Xcode project."

khandpur · 2017-03-28T07:43:07Z

docs/install-and-run.md


 ### GitHub Installation

 In cases where CocoaPods is not compatible with your project, you can add EarlGrey manually to your Xcode project.

 #### Step 1: Generate EarlGrey.framework

-  1. Download the source for EarlGrey and its dependencies.
-     * Download EarlGrey's source code from the [Latest Release](https://github.com/google/EarlGrey/archive/1.0.0.zip)
+   1. Download the source for EarlGrey.


How is this 1. different from 1. below? Can you please view the files in md viewer and fix all the rendering / layout issues?

Removed the extra 1.

khandpur · 2017-03-28T07:43:59Z

docs/install-and-run.md


 #### Step 2: Add EarlGrey as a dependency of the project which contains your app under test

-  1. Close **EarlGrey.xcodeproj** so that it is no longer open in any Xcode window. Once closed, drag **EarlGrey.xcodeproj** from its directory into your App’s project or workspace in Xcode. To verify this, you should find `EarlGrey` in the list of targets of your app in Xcode:
+   1. Close **EarlGrey.xcodeproj** so that it is no longer   


why the abrupt break in line after "no longer" ?

khandpur · 2017-03-28T07:44:31Z

docs/install-and-run.md

-
-  3. Add EarlGrey as a Target Dependency to the Test Target:
+      ```
+      **Project** → **Test Target** → **Build Phases** → **Link Binary With Libraries** → **+ (Add Sign)** → **EarlGrey.framework**


** isn't bolding the texts

plz view in md viewer and fix such issues. I've spotted a lot of them already.

Yeah, ** doesn't work in code blocks. Removed em.

sid-github · 2017-03-29T23:49:29Z

docs/install-and-run.md

-  1. Download the source for EarlGrey and its dependencies.
-     * Download EarlGrey's source code from the [Latest Release](https://github.com/google/EarlGrey/archive/1.0.0.zip)
+   1. Download EarlGrey's source code from the
+      [Latest Release](https://github.com/google/EarlGrey/releases/tag/1.8.0).


Lets link to https://github.com/google/EarlGrey/releases instead, the latest will be on the top any ways otherwise we will have to keep updating this link

@khandpur could we confirm this?

or https://github.com/google/EarlGrey/releases/latest

+1 to hao's idea

khandpur

Minor nits.

khandpur · 2017-03-30T00:02:28Z

docs/faq.md

@@ -1,5 +1,14 @@
 # FAQ

+**I did a fresh `git clone` of the EarlGreyExample CocoaPods Demo project followed by a


He plans on getting it in for the next release so lets remove this? we might forget to not remove it.

khandpur · 2017-03-30T00:22:23Z

README.md

@@ -46,6 +46,7 @@ You can also start new discussions with us on our [Google group](https://groups.
 or request to join our [slack channel](https://googleoss.slack.com/messages/earlgrey).

  * [FAQ](https://github.com/google/EarlGrey/tree/master/docs/faq.md)


FAQ - Frequently Asked Questions

khandpur · 2017-03-30T00:35:39Z

docs/faq.md

+
+```swift
+// Objective-C
+[GREYTestHelper enableFastAnimation];
 ```

 If the above doesn't help, you can temporarily disable synchronization to work around an animation


Nit: place the swift code example before objc.

googlebot added the cla: yes label Mar 17, 2017

khandpur reviewed Mar 18, 2017

View reviewed changes

Update docs and make them more lean

87bf9a5

tirodkar force-pushed the docsUpdate branch 6 times, most recently from 71e5def to c6876c1 Compare March 20, 2017 07:46

bootstraponline reviewed Mar 20, 2017

View reviewed changes

tirodkar force-pushed the docsUpdate branch from c6876c1 to 873479d Compare March 20, 2017 18:32

tirodkar commented Mar 20, 2017

View reviewed changes

AVandelay reviewed Mar 20, 2017

View reviewed changes

Add review fixes

43f630c

tirodkar force-pushed the docsUpdate branch from 873479d to 43f630c Compare March 20, 2017 19:00

bootstraponline approved these changes Mar 20, 2017

View reviewed changes

khandpur requested changes Mar 23, 2017

View reviewed changes

tirodkar force-pushed the docsUpdate branch 5 times, most recently from 2bec234 to 81fe48d Compare March 27, 2017 06:17

Update documents and added ifaq.md as per the comments

7e5b64c

tirodkar force-pushed the docsUpdate branch from 81fe48d to 7e5b64c Compare March 27, 2017 06:18

khandpur requested changes Mar 28, 2017

View reviewed changes

sid-github approved these changes Mar 29, 2017

View reviewed changes

khandpur approved these changes Mar 30, 2017

View reviewed changes

tirodkar force-pushed the docsUpdate branch from f321fd2 to 22fee5b Compare March 30, 2017 01:34

More fixes

604dfd0

tirodkar force-pushed the docsUpdate branch from 22fee5b to 604dfd0 Compare March 30, 2017 01:42

khandpur approved these changes Mar 30, 2017

View reviewed changes

khandpur added the lgtm label Mar 30, 2017

khandpur merged commit b8c746b into google:master Mar 30, 2017


		<img src="images/image00.png" width="500">
		Click Next → "Add a Test Target Name" → Finish.


		2. As part of the initial build step, a script setup-earlgrey.sh will be run to download all the required dependencies. Without it, you might find dependencies like `fishhook` and `OCHamcrest` shown as missing in the folder structure.
		2. As part of the initial build step, a script setup-earlgrey.sh will be run to download all the


		* Unzip and go to the `EarlGrey-1.0.0/EarlGrey` directory that contains EarlGrey.xcodeproj.
		* Unzip and go to the `EarlGrey-1.0.0/EarlGrey` directory that contains EarlGrey.xcodeproj.

		@@ -263,40 +275,39 @@ your test and in your application code and use the built-in tools seamlessly.

		### Swift

		@@ -1,5 +1,14 @@
		# FAQ

		**I did a fresh `git clone` of the EarlGreyExample CocoaPods Demo project followed by a


		### CocoaPods installation
		For EarlGrey, we highly recommend [CocoaPods](http://cocoapods.org/pods/EarlGrey) as the best way to get started.

		@@ -46,6 +46,7 @@ You can also start new discussions with us on our [Google group](https://groups.
		or request to join our [slack channel](https://googleoss.slack.com/messages/earlgrey).

		* [FAQ](https://github.com/google/EarlGrey/tree/master/docs/faq.md)

Update docs and make them more lean #458

Update docs and make them more lean #458

Conversation

tirodkar commented Mar 17, 2017

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

AVandelay Mar 20, 2017 • edited

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Step 3: Open workspace and verify that you see EarlGrey.

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

AVandelay Mar 20, 2017 •

edited