Skip to content
This repository has been archived by the owner on Jan 15, 2021. It is now read-only.

Tests: Fix failing tests on Android #1905

Open
jareksl opened this issue Jun 12, 2017 · 0 comments
Open

Tests: Fix failing tests on Android #1905

jareksl opened this issue Jun 12, 2017 · 0 comments
Labels

Comments

@jareksl
Copy link
Member

jareksl commented Jun 12, 2017

All tests pass in case when there are two devices used. In case of three devices, some of tests are failing. It is not deterministic. All failing tests passes without problems when executed separately.

Tests below fail on android devices:

  1. testThaliMobileNative.js
  • Can connect to a remote peer
  • Can shift data securely
  • discoveryAdvertisingStateUpdateNonTCP is called
  • peerAvailabilityChange is called
  1. testThaliMobileNativeAndroid.js
  • Get error when trying to double connect to a peer on Android
  • #startUpdateAdvertisingAndListening - destroying the local connection kills the connection to the remote peer
  • #startUpdateAdvertisingAndListening - ending the local connection
  • #startUpdateAdvertisingAndListening - ending remote peers connection kills the local connection
  1. testThaliNotification.js
  • Client to server request coordinated
  1. testThaliMobileNativeWrapper.js
  • We provide notification when a listener dies and we recreate it
  1. testThaliPullReplicationFromNotificationCoordinated.js
  • Coordinated pull replication from notification test
  1. testThaliMobile
  • test for data corruption - 'TypeError: serversManager is null'
@jareksl jareksl added the Node label Jun 12, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant