web-platform-tests/wpt

Add a test for the reason in the websocket close handshake

Open

#2253 opened on Oct 14, 2015

View on GitHub
 (0 comments) (0 reactions) (0 assignees)HTML (4,581 stars) (2,898 forks)batch import
good first issuetype:missing-coveragewebsockets

Description

https://github.com/servo/servo/pull/7871 pointed out this is untested right now.

Contributor guide

Tech stack
javascripthtml
Domain
testing
Issue type
test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
basic knowledge of websocketsfamiliarity with wpt test framework
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85
Research direction
The issue is to add a test for the reason in the WebSocket close handshake, as pointed out in https://github.com/servo/servo/pull/7871. The test should verify that the close reason is correctly transmitted and can be accessed. Look at existing WebSocket tests in the repository for patterns, and write a new test file or extend an existing one.