ExternalVendorCode/balena-supervisor
1
0
Fork 0
mirror of https://github.com/balena-os/balena-supervisor.git synced 2025-01-31 08:25:36 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

test: Use longer delays in logger tests

Browse Source 
We've seen at least one case where the 10ms delay
wasn't enough, causing the tests to fail where they shouldn't.

(Ideally we should find a better way to detect when the streams
have finished propagating, but this will avoid failures in the meantime).

Change-type: patch
Signed-off-by: Pablo Carranza Velez <pablo@balena.io>
This commit is contained in:
Pablo Carranza Velez 2018-10-25 13:36:53 -07:00
parent 66b46cffd7
commit 1e47d0c434
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
test/12-logger.spec.coffee
View File

@ -45,7 +45,7 @@ describe 'Logger', ->
clock.tick(4999)
clock.restore()
Promise.delay(10)
Promise.delay(100)
.then =>
expect(@_req.body).to.equal('')
@ -55,7 +55,7 @@ describe 'Logger', ->
clock.tick(61000)
clock.restore()
Promise.delay(10)
Promise.delay(100)
.then =>
expect(@_req.end.calledOnce).to.be.true
@ -80,7 +80,7 @@ describe 'Logger', ->
})
# small delay for the streams to propagate data
Promise.delay(10)
Promise.delay(100)
.then =>
lines = @_req.body.split('\n')
expect(lines.length).to.equal(3)
@ -97,7 +97,7 @@ describe 'Logger', ->
clock.tick(10000)
clock.restore()
Promise.delay(10)
Promise.delay(100)
.then =>
expect(@fakeEventTracker.track).to.be.calledWith('Some event name', { someProp: 'someVal' })
lines = @_req.body.split('\n')