Closed lesn1kk closed 7 years ago
PR is added to the queue for testing as 1. task. (8171119)
Test 121958569 (8171119) build started.
Test (Success) 121958569 build is completed (8171119)
See https://github.com/ThaliTester/TestResults/tree/1219585698171119_Fix_failing_test_on_iOS_devices__1871_mlesnic/ for the logs
Test 1219585698171119(8171119) has failed
See https://github.com/ThaliTester/TestResults/tree/1219585698171119_Fix_failing_test_on_iOS_devices__1871_mlesnic/ for the fail logs
Reviewed 1 of 1 files at r1. Review status: all files reviewed at latest revision, all discussions resolved.
Comments from Reviewable
Review status: :shipit: all files reviewed at latest revision, all discussions resolved, all commit checks successful.
Comments from Reviewable
Reviewed 1 of 1 files at r1. Review status: :shipit: all files reviewed at latest revision, all discussions resolved, all commit checks successful.
Comments from Reviewable
Comments from Reviewable
First of all, before starting this test we need to make sure that ThaliMobile is started. Otherwise,
networkChangedNonTCP
events will be filtered out.Based on test assumptions that we discover 1 peer via WiFi and 1 peer via MPCF, we can safely assume that phone is connected to access point so the
bbsidName
field is set to some non null value. This is becausenetworkChangedValue
withbssidName
set to null is treated same as WiFi off. See #1500 and #1707 for details.Also, since this scenario assume that after disabling WiFi
peerAvailabilityChanged
event would be fired twice, we need to increaseavailibilityHandler
calls limit by one.This change is