You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: `assembleDebug` has to be run before `connectedCheck`. See [bug](https://code.google.com/p/android/issues/detail?id=180689), which will be fixed in 1.3.1 .
121
-
122
120
##### From command-line via adb
123
121
You need to install the app and test app first:
124
122
@@ -181,7 +179,7 @@ Since Gradle Android Plugin version 1.2.0 using ProGuard has become a lot easier
181
179
To try it out just uncomment the minify section for the debug build type in the app modules `build.gradle` file.
182
180
183
181
## Custom Gradle command-line arguments
184
-
Gradle allows you to pass custom arguments to `AndroidJUnitRunner`. This is equivalent to running `adb shell am instrument -w -e <argName> <argValue>`.
182
+
Gradle allows you to pass custom arguments to `AndroidJUnitRunner`. This is equivalent to running `adb shell am instrument -w -e <argName> <argValue> com.example.android.testing.blueprint.test/android.support.test.runner.AndroidJUnitRunner`.
185
183
Custom arguments can be particularly useful when you just want to run a specific test class/method/qualifier.
186
184
187
185
To pass a custom argument the -Pcom.android.tools.instrumentationTestRunnerArgs=argName=argValue
@@ -190,19 +188,19 @@ property needs to be used, in conjunction with `argName` and `argValue`. Multipl
190
188
For instance, to run all tests annotated with the `@Large` test size qualifier in the app module, execute:
0 commit comments