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] [Closed] (EDGENT-438) Enhance WebSocketClientTest's "skip if can't connect"
Date Tue, 02 Jan 2018 18:25:01 GMT

     [ https://issues.apache.org/jira/browse/EDGENT-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dale LaBossiere closed EDGENT-438.
----------------------------------
       Resolution: Fixed
    Fix Version/s: Apache Edgent 1.2.0

> 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
>             Fix For: Apache Edgent 1.2.0
>
>
> 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