summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorParménides GV <parmegv@sdf.org>2014-07-10 18:32:55 +0200
committerParménides GV <parmegv@sdf.org>2014-07-24 16:50:48 +0200
commit98f2fcedc3c645b38ecf168d57e28287c4a7a76e (patch)
tree8d1179ef5f48041b242d04cc362afcdb84c67de9
parent629a0b279a80938212b01c096e55c402d91739d4 (diff)
Simulate network down.
The tests say they failed, but it's because the adb server is no longer able to communicate with the emulator due to switching network connectivity off (and being the adb server connected to a local tcp port of the emulator, this port dissapears once connectivity is down). To see if all tests passed, take a look at the logcat. Once tests are finished, issue "adb kill-server" from the development machine, and then "adb logcat".
-rw-r--r--app/src/androidTest/java/se/leap/bitmaskclient/test/testDashboard.java7
1 files changed, 3 insertions, 4 deletions
diff --git a/app/src/androidTest/java/se/leap/bitmaskclient/test/testDashboard.java b/app/src/androidTest/java/se/leap/bitmaskclient/test/testDashboard.java
index 85197493..66ef6565 100644
--- a/app/src/androidTest/java/se/leap/bitmaskclient/test/testDashboard.java
+++ b/app/src/androidTest/java/se/leap/bitmaskclient/test/testDashboard.java
@@ -48,14 +48,13 @@ public class testDashboard extends ActivityInstrumentationTestCase2<Dashboard> {
if(!solo.waitForText(getActivity().getString(R.string.eip_state_not_connected)))
fail();
- /*ConnectionManager.setMobileDataEnabled(false, solo.getCurrentActivity().getApplicationContext());
+ ConnectionManager.setMobileDataEnabled(false, solo.getCurrentActivity().getApplicationContext());
solo.clickOnView(solo.getView(R.id.eipSwitch));
- if(!solo.waitForText(getActivity().getString(R.string.eip_status_start_pending)))
- fail();
+ // if(!solo.waitForText(getActivity().getString(R.string.eip_status_start_pending)))
+ // fail();
if(!solo.waitForText(getActivity().getString(R.string.state_nonetwork)))
fail();
- */
}
public void testLogInAndOut() {