bitmask_android.git, branch 0.5.4 [bitmask_android] Merge branch 'develop' 2014-07-24T14:51:45+00:00 Parménides GV parmegv@sdf.org 2014-07-24T14:51:45+00:00 1dd922cf3c00bdee4625663e436286fa39e566e5 






Merge branch 'release-0.5.4' into develop
2014-07-24T14:50:58+00:00

Parménides GV
parmegv@sdf.org

2014-07-24T14:50:58+00:00

b28eeb08e8ec3baafdd9388cc5b70c6c84db9cf1












Bump version number for the "meetup" release
2014-07-24T14:50:48+00:00

Parménides GV
parmegv@sdf.org

2014-07-21T15:10:31+00:00

dce7064c35a903c7b13e97181c07058e143df621












Changelog for 0.5.4
2014-07-24T14:50:48+00:00

Parménides GV
parmegv@sdf.org

2014-07-21T15:09:34+00:00

a572fbf2a1f69fbba80d28f3c425defdcf5dc633












Bump build number and version for 0.6.0-RC1
2014-07-24T14:50:48+00:00

Parménides GV
parmegv@sdf.org

2014-07-15T16:29:37+00:00

b8165c50328beca82efc93fadfc69a3ac18123dc












Some instructions to run the tests.
2014-07-24T14:50:48+00:00

Parménides GV
parmegv@sdf.org

2014-07-15T16:27:02+00:00

1d6c26020a8ecc71a97cbbd313c776984afd903a












network up & down 3 times: sometimes fails
2014-07-24T14:50:48+00:00

Parménides GV
parmegv@sdf.org

2014-07-10T18:55:55+00:00

623f81b5e52a5155549731e4afe35ca054f97a3f

I simulate removing the network at the end of the test.

Sometimes, the test fails because a openvpn tries to close a bad file
descriptor.





I simulate removing the network at the end of the test.

Sometimes, the test fails because a openvpn tries to close a bad file
descriptor.







Simulate network down.
2014-07-24T14:50:48+00:00

Parménides GV
parmegv@sdf.org

2014-07-10T16:32:55+00:00

98f2fcedc3c645b38ecf168d57e28287c4a7a76e

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".





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".







We don't need support library from Robotium.
2014-07-24T14:50:48+00:00

Parménides GV
parmegv@sdf.org

2014-07-10T10:40:26+00:00

629a0b279a80938212b01c096e55c402d91739d4

I've also fixed a simple test that wasn't letting the suite to finish
correctly.





I've also fixed a simple test that wasn't letting the suite to finish
correctly.







Minor gradle updates, due to Android L.
2014-07-24T14:50:48+00:00

Parménides GV
parmegv@sdf.org

2014-07-10T09:05:58+00:00

c552639de6e6192654c9aea02e89d6541baa3857

- Build tools update to latest version (20).
- testPackageName is correctly calculated by default, doing nothing.
- support library needs some tweaks to support pre Android L versions.





- Build tools update to latest version (20).
- testPackageName is correctly calculated by default, doing nothing.
- support library needs some tweaks to support pre Android L versions.