In fixing #359, I noticed that some of the later tests failed randomly.
In an earlier test, a timeout is set to assert(fail) after 100ms to catch the situation where a DeviceDiscovery does not issue a timeout event when it should.
If the test passes, then the rogue timeout is left hanging to fire 100ms later, disrupting later tests.
In fixing #359, I noticed that some of the later tests failed randomly.
In an earlier test, a timeout is set to
assert(fail)
after 100ms to catch the situation where aDeviceDiscovery
does not issue atimeout
event when it should.If the test passes, then the rogue timeout is left hanging to fire 100ms later, disrupting later tests.
https://github.com/bencevans/node-sonos/blob/851a5355cd014d794b3887ce74dee1cc3cacdef1/test/sonos.test.js#L314-L327
PR to fix on the way