LayoutTests/http/tests/websocket/invalid-encode-length-expected.txt - Issue 817733004: WebSocket layout tests clean up

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Unified Diff: LayoutTests/http/tests/websocket/invalid-encode-length-expected.txt

Issue 817733004: WebSocket layout tests clean up (Closed) Base URL: https://chromium.googlesource.com/chromium/blink.git@master

Patch Set: Created 5 years, 11 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View side-by-side diff with in-line comments

Download patch

« no previous file with comments | « LayoutTests/http/tests/websocket/invalid-encode-length.html ('k') | LayoutTests/http/tests/websocket/invalid-masked-frames-from-server.html » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

Index: LayoutTests/http/tests/websocket/invalid-encode-length-expected.txt

diff --git a/LayoutTests/http/tests/websocket/invalid-encode-length-expected.txt b/LayoutTests/http/tests/websocket/invalid-encode-length-expected.txt

index 9cc40777af083ee0e3b6559e4a1c43c99eeda46d..bca8ac5bb905124e5b8ed3d59570bdaf706ff4af 100644

--- a/LayoutTests/http/tests/websocket/invalid-encode-length-expected.txt

+++ b/LayoutTests/http/tests/websocket/invalid-encode-length-expected.txt

@@ -8,18 +8,22 @@ On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE

Case 126_125: Test started.

onopen() was called.

+PASS onerror() was called

onclose() was called.

PASS closeEvent.wasClean is false

Case 126_0: Test started.

onopen() was called.

+PASS onerror() was called

onclose() was called.

PASS closeEvent.wasClean is false

Case 127_65535: Test started.

onopen() was called.

+PASS onerror() was called

onclose() was called.

PASS closeEvent.wasClean is false

Case 127_0: Test started.

onopen() was called.

+PASS onerror() was called

onclose() was called.

PASS closeEvent.wasClean is false

PASS successfullyParsed is true