edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dale LaBossiere (JIRA)" <j...@apache.org>
Subject [jira] [Created] (EDGENT-438) Enhance WebSocketClientTest's "skip if can't connect"
Date Mon, 20 Nov 2017 22:21:00 GMT
Dale LaBossiere created EDGENT-438:
--------------------------------------

             Summary: Enhance WebSocketClientTest's "skip if can't connect"
                 Key: EDGENT-438
                 URL: https://issues.apache.org/jira/browse/EDGENT-438
             Project: Edgent
          Issue Type: Test
            Reporter: Dale LaBossiere
            Assignee: Dale LaBossiere


At my work location, WebSocketClientTest.skipTestIfCantConnect() to the public websocket server
succeeds but subsequently, when the connector creates the real websocket and connects, that
fails with 
`Didn't switch protocols, expected status <101>, but got <403>`... which causes
a test failure.

For some reason my work location isn't allowing a websocket connect to that public server.
 These tests run fine from other locations (e.g., home, the CI servers).

Basically, enhance the connect test code to do a real websocket connect instead of just a
simple socket.connect().



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message