README.md in screengrab-0.2.0 vs README.md in screengrab-0.2.1
- old
+ new
@@ -31,37 +31,31 @@
[](https://twitter.com/FastlaneTools)
[](https://github.com/fastlane/screengrab/blob/master/LICENSE)
[](http://rubygems.org/gems/screengrab)
-### Automates screenshots of your Android app
+###### Automated localized screenshots of your Android app on every device
-Screengrab is a commandline tool that automates taking localized screenshots of your Android app.
-
<img src="assets/running-screengrab.gif" width="640">
### Why should I automate this process?
- Create hundreds of screenshots in multiple languages on emulators or real devices, saving you hours
- Easily verify that localizations fit into labels on all screen dimensions to find UI mistakes before you ship
- You only need to configure it once for anyone on your team to run it
- Keep your screenshots perfectly up-to-date with every app update. Your customers deserve it!
- Fully integrates with [`fastlane`](https://fastlane.tools) and [`supply`](https://github.com/fastlane/supply)
# Installation
+Install the gem
-Once this tool is officially released, the installation will be as simple as running `gem install screengrab` For the private alpha, please follow these testing instructions:
+```
+sudo gem install screengrab
+```
-##### Command line tool installation
-1. Clone the repo with `git clone git@github.com:fastlane/screengrab.git`
-1. `cd` into your screengrab repo directory and run `rake install`
- - You may need to `gem install bundler` if you don't already have bundler
- - If you're using the default Ruby on Mac OS you may need to use `sudo`
-1. Run `screengrab init` to complete installation
-
##### Gradle dependency
```java
-androidTestCompile 'tools.fastlane:screengrab:0.1.1'
+androidTestCompile 'tools.fastlane:screengrab:0.2.0'
```
##### Configuring your Manifest Permissions
Ensure that the following permissions exist in your **src/debug/AndroidManifest.xml**
@@ -142,10 +136,10 @@
Screengrab.screenshot("after_button_click");
}
}
```
-There is an [example project](https://github.com/fastlane/screengrab/tree/master/example/src/androidTest/java/io/fabric/localetester) showing how to use use JUnit 3 or 4 and Espresso with the screengrab Java library to capture screenshots during a UI test run.
+There is an [example project](https://github.com/fastlane/screengrab/tree/master/example/src/androidTest/java/tools/fastlane/localetester) showing how to use use JUnit 3 or 4 and Espresso with the screengrab Java library to capture screenshots during a UI test run.
Using JUnit 4 is preferable because of its ability to perform actions before and after the entire test class is run. This means you will change the device's locale far fewer times when compared with JUnit 3 running those commands before and after each test method.
When using JUnit 3 you'll need to add a bit more code: