e2e testing of p2p sync #835
Replies: 2 comments
-
I wrote to BrowserStack about support for device -> device communication in their testing environment, and they replied:
I suspect this is going to be the case with a lot of real-device automated testing, so I think our only way to test p2p sync will be to figure out how to configure the networking stack for emulators, then we can simulate network environments. |
Beta Was this translation helpful? Give feedback.
-
The KDEConnect docs for Android Emulator have been recently updated and include good details about how to configure QEMU networking for broadcast packets in Android APK > 24. |
Beta Was this translation helpful? Give feedback.
-
I did some digging into testing p2p sync over a local network in (multiple) Android emulators. Unfortunately it's really hard (impossible?) because the emulators are on their own separate subnet and it's not possible to even ping them (see local networking limitations).
What we would like is to set up two or more emulators and test local network discovery and sync between them, and, if possible, simulate different network conditions. Mapeo currently does not do discovery over the internet, only local WiFi.
There are some ways around this for older versions of the Android APK, with an excellent write up by @rubdos and some details from @manojrege but it does not work with Android SDK >=25, which set up multiple networks in the emulator.
It's maybe possible to use a similar approach to above with the new networking stack, but it's much more complicated - it would need an understanding of the Android source code for networking, and understanding how Qemu works. This article might also be helpful: https://community.kde.org/KDEConnect/Android_Emulator
Beta Was this translation helpful? Give feedback.
All reactions