Migrate ConnectionTest e2e tests to use POP

[niklasberglund]

Migrated the e2e test cases in ConnectionTest to follow Page Object Pattern, similar to how we implemented it in LoginTests. The changes can be tested by running all test cases under ConnectionTest.

Also implemented Wireguard obfuscation set to automatic with UDP traffic to relay blocked connection test(testWireGuardObfuscationAutomatic).

Fixes DROID-1600, DROID-1622

---

This change is 

[linear]

DROID-1600 E2E test connecting to relay with WG obfuscation set to automatic

DROID-1622 Migrate ConnectionTest tests to use POP

[Rawa]

Reviewed 4 of 12 files at r1, all commit messages.
Reviewable status: 4 of 12 files reviewed, 2 unresolved discussions (waiting on @niklasberglund)

---

android/test/e2e/src/main/kotlin/net/mullvad/mullvadvpn/test/e2e/ConnectionTest.kt line 176 at r1 (raw file):

            on<SystemVpnConfigurationAlert> { clickOk() }

            var relayIpAddress: String? = null

Ping me and we can talk about this, I would like to avoid the var's

---

android/test/e2e/src/main/kotlin/net/mullvad/mullvadvpn/test/e2e/ConnectionTest.kt line 215 at r1 (raw file):

            clickLocalNetworkSharingSwitch()
            pressBack()
            pressBack()

A bit misleading because this pressBack is probably on SettingsPage rather than VpnSettingsPage.

[niklasberglund]

Reviewable status: 4 of 12 files reviewed, 2 unresolved discussions (waiting on @Rawa)

---

android/test/e2e/src/main/kotlin/net/mullvad/mullvadvpn/test/e2e/ConnectionTest.kt line 176 at r1 (raw file):

Previously, Rawa (David Göransson) wrote…

Ping me and we can talk about this, I would like to avoid the var's

Perfect. Me too 👍

---

android/test/e2e/src/main/kotlin/net/mullvad/mullvadvpn/test/e2e/ConnectionTest.kt line 215 at r1 (raw file):

Previously, Rawa (David Göransson) wrote…

A bit misleading because this pressBack is probably on SettingsPage rather than VpnSettingsPage.

True! Actually the pressBack() function in Page is maybe a bit misleading, because it uses the Android back functionality, it doesn't press the back arrow in the settings view. I'm torn. On one hand it's nice to shorten the syntax, on the other hand it's misleading and maybe more descriptive to do uiDevice.pressBack(), on the third hand maybe the tests should actually press the back button instead of using the Android back functionality.

[Rawa]

Reviewable status: 4 of 12 files reviewed, 1 unresolved discussion

---

android/test/e2e/src/main/kotlin/net/mullvad/mullvadvpn/test/e2e/ConnectionTest.kt line 176 at r1 (raw file):

Previously, niklasberglund (Niklas Berglund) wrote…

Perfect. Me too 👍

Seems like we are a bit limited by the type system. 😢

[niklasberglund]

Reviewable status: 4 of 14 files reviewed, 1 unresolved discussion (waiting on @Rawa)

---

android/test/e2e/src/main/kotlin/net/mullvad/mullvadvpn/test/e2e/ConnectionTest.kt line 215 at r1 (raw file):

Previously, niklasberglund (Niklas Berglund) wrote…

True! Actually the pressBack() function in Page is maybe a bit misleading, because it uses the Android back functionality, it doesn't press the back arrow in the settings view. I'm torn. On one hand it's nice to shorten the syntax, on the other hand it's misleading and maybe more descriptive to do uiDevice.pressBack(), on the third hand maybe the tests should actually press the back button instead of using the Android back functionality.

We talked about this over a Slack huddle. Have removed pressBack() from Page and using device.pressBack() instead, and also moved them out of the page scopes.

[Rawa]

Reviewed 2 of 12 files at r1, 7 of 8 files at r2, 1 of 1 files at r3, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved