aboutsummaryrefslogtreecommitdiffhomepage
path: root/src/objective-c/tests/Connectivity/README.md
diff options
context:
space:
mode:
authorGravatar Muxi Yan <mxyan@google.com>2018-02-26 16:22:37 -0800
committerGravatar Muxi Yan <mxyan@google.com>2018-02-26 16:22:37 -0800
commit3cec602aeb7c8bf4d368990bf9b837800bd780e3 (patch)
tree85890369668e26d56542a05dfc37c4206edaaa5f /src/objective-c/tests/Connectivity/README.md
parent0dc7c5996ce5091a96632919a3e3befe351b44d0 (diff)
Rewrite connectivity testing app
Diffstat (limited to 'src/objective-c/tests/Connectivity/README.md')
-rw-r--r--src/objective-c/tests/Connectivity/README.md12
1 files changed, 5 insertions, 7 deletions
diff --git a/src/objective-c/tests/Connectivity/README.md b/src/objective-c/tests/Connectivity/README.md
index 851cb9d1da..907821e800 100644
--- a/src/objective-c/tests/Connectivity/README.md
+++ b/src/objective-c/tests/Connectivity/README.md
@@ -2,14 +2,12 @@ This app can be used to manually test gRPC under changing network conditions.
It makes RPCs in a loop, logging when the request is sent and the response is received.
-To test on the simulator, run `pod install`, open the workspace created by Cocoapods, and run the app.
-Once running, disable WiFi (or ethernet) _in your computer_, then enable it again after a while. Don't
-bother with the simulator's WiFi or cell settings, as they have no effect: Simulator apps are just Mac
-apps running within the simulator UI.
+To test on the simulator, run `pod install`, open the workspace created by Cocoapods, and run the
+app on an iOS device. Once running, tap a few times of each of the two buttons to make a few unary and streaming
+calls. Then disable/enable different network interfaces (WiFi, cellular) on your device.
-The expected result is to never see a "hanged" RPC: success or failure should happen almost immediately
-after sending the request. Symptom of a hanged RPC is a log like the following being the last in your
-console:
+The expected behavior is that the pending streaming calls fails immediately with error UNAVAILABLE.
+Moreover, when network comes back, new calls have the same behavior.
```
2016-06-29 16:51:29.443 ConnectivityTestingApp[73129:3567949] Sending request.