1
84%
master: 84%

Ran 16 Nov 2017 10:41PM UTC

Files 47

Run time 1s

Badge

Embed ▾

Committed 16 Nov 2017 10:39PM UTC coverage: 81.342% (+0.01%) from 81.33%

Job # DARTANALYZER_FLAGS='--fatal-warnings --strong'

Build Type

push

travis-ci

Committed by

cbracken

Commit Message

Use FIFO timer ordering in FakeAsync (#265)

As noted in https://github.com/google/quiver-dart/issues/258, the
current ordering of _getNextTimer() in _FakeAsync is inconsistent with
the native Dart event loop.

In the process of fixing that, I had to fix a few other idiosyncrasies
that were revealed from the existing unit tests which relied on the
incorrect behavior. For instance, if you had a periodic timer occur at
the same time as a delayed timer, whether or not both of them were
"flushed" in flushTimers depended on the order with which they were
queued. Now it does not.

Run Details

1212 of 1490 relevant lines covered (81.34%)

1.54 hits per line

google / quiver-dart / 434 / 1
84%
master: 84%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 434.1 (DARTANALYZER_FLAGS='--fatal-warnings --strong')

google / quiver-dart / 434 / 1 84% master: 84%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 434.1 (DARTANALYZER_FLAGS='--fatal-warnings --strong')

google / quiver-dart / 434 / 1
84%
master: 84%

README BADGES
x