Permalink
Browse files

Added readme references to the new MPE Sample

  • Loading branch information...
nkoroste committed Jul 25, 2017
1 parent 364e38c commit ec68073a0a6685bca48869128e4afeae63c1ce97
Showing with 23 additions and 2 deletions.
  1. +2 −2 README.md
  2. +21 −0 ui/espresso/MultiProcessSample/README.md
View
@@ -24,6 +24,8 @@ A collection of samples demonstrating different frameworks and techniques for au
**[WebBasicSample](https://github.com/googlesamples/android-testing/blob/master/ui/espresso/WebBasicSample)** - Use Espresso-web to interact with WebViews
**[BasicSampleBundled](https://github.com/googlesamples/android-testing/blob/master/ui/espresso/BasicSampleBundled)** - Basic sample for Eclipse and other IDEs
**[MultiProcessSample](https://github.com/googlesamples/android-testing/blob/master/ui/espresso/MultiProcessSample)** - Showcases how to use multiprocess Espresso.
### UiAutomator Sample
**[BasicSample](https://github.com/googlesamples/android-testing/tree/master/ui/uiautomator/BasicSample)** - Basic UI Automator sample
@@ -94,5 +96,3 @@ distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
License for the specific language governing permissions and limitations under
the License.
@@ -0,0 +1,21 @@
# Multiprocess Espresso Sample
To test app components in a non-default processes, you can use the functionality of Multiprocess Espresso. This tool, available on Android O (API level 26) and higher, allows you to seamlessly test your app's UI interactions that cross your app's process boundaries while maintaining Espresso's synchronization guarantees.
1. Download the project code, preferably using `git clone`.
1. In Android Studio, select *File* | *Open...* and point to the `./build.gradle` file.
1. Check out the relevant code:
* The application under test is located in `src/main/java`
* Tests are in `src/androidTest/java`
1. Create the test configuration:
* Open *Run* menu | *Edit Configurations*
* Add a new *Android Tests* configuration
* Choose a module
1. Connect a device or start an emulator
* Turn animations off.
(On your device, under Settings->Developer options disable the following 3 settings: "Window animation scale", "Transition animation scale" and "Animator duration scale")
1. Run the newly created configuration
The application will be started on the device/emulator and a series of actions will be performed automatically.
If you are using Android Studio, the *Run* window will show the test results.

0 comments on commit ec68073

Please sign in to comment.