In practice, all tests that uses MPCF might fail because of zombie. Here is a list that I created by running tests on 2 iOS devices with iOS 10.3.1 in NATIVE mode (in BOTH mode results are the same).
testThaliMobileNativeWrapper - can still do HTTP requests between peers with coordinator
testThaliMobileNativeWrapper - can do HTTP requests after connections are cut
testThaliManagerCoordinated - test write
testThaliMobileNative - Can connect to a remote peer
testThaliMobileNative - Can shift data
testThaliMobileNative - Can shift data via parallel connections
testThaliMobileNative - Can shift data securely
testThaliMobileNative - Can shift large amounts of data
testThaliMobileNativeiOS - Get same port when trying to connect multiple times on iOS
testThaliMobile - can get data from all participants
testThaliNotification - Client to server request coordinated
testThaliPullReplicationFromNotificationCoordinated - Coordinated pull replication from notification test
testThaliReplicationPeerActionCoordinated - Coordinated replication action test - each device has the same local db name
testThaliReplicationPeerActionCoordinated - Coordinated replication action test - each device has different local db name
testThaliReplicationPeerActionCoordinated - Coordinated replication action test - should throw error when wrong remote db name is provided
testHttp - Single coordinated request ios native
testHttp - Multiple coordinated request ios native
jareksl
commented
7 years ago
In practice, all tests that uses MPCF might fail because of zombie. Here is a list that I created by running tests on 2 iOS devices with iOS 10.3.1 in NATIVE mode (in BOTH mode results are the same).