31
97%

Ran 09 Oct 2015 12:27AM CUT

Jobs 1

Files 2

Run time 0s

Badge

Embed ▾

pending completion

Build # 31

Build Type

push

travis-ci

Committed by

preaction

Commit Message

fix test failure when re-using Test::Mojo object

The Test::Mojo object, when used in WebSocket mode, stores some state
about the WebSocket to create some blocking loops, running the event
loop until an action is completed (like closing the socket).

This is a problem when we swap out the transaction in a given Test::Mojo
object: The state of the Test::Mojo object does not match the state of
the inner transaction, causing unexpected consequences.

This revealed itself when we closed a push/pull socket halfway through
the test, to ensure the round-robin was happening correctly. The next
message test would fail because the message was not yet sent.

The solution is to have a single app object, and multiple Test::Mojo
objects that all share the same app. The Test::Mojo object is used for
the duration of that socket.

Fixes #18

Run Details

127 of 127 relevant lines covered (100.0%)

4.35 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
9	31.9 (COVERAGE=1)	09 Oct 2015 12:27AM CUT	2	100.0	Travis Job 31.9

Source Files on build 31

Show entries

Search:

Coverage	∆	File	Lines	Relevant	Covered	Missed	Hits/Line
100.0		lib/Mercury.pm	285	90	90	0	4.0
100.0		lib/Mercury/PushPull.pm	165	37	37	0	4.0 + 1.0

Showing 1 to 2 of 2 entries

preaction / Mercury / 31
97%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 31

preaction / Mercury / 31 97%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 31

preaction / Mercury / 31
97%

README BADGES
x