LayoutTests/editing/spelling/spelling-huge-text-expected.txt - Issue 23534071: Use shouldBecomeEqual in asynchronous spellchecking tests.

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/editing/spelling/spelling-huge-text-expected.txt

Issue 23534071: Use shouldBecomeEqual in asynchronous spellchecking tests. (Closed) Base URL: https://chromium.googlesource.com/chromium/blink@master

Patch Set: Apply Tony's review and use asynchronous spellchecking in two tests Created 7 years, 3 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/editing/spelling/spelling-huge-text.html ('k') | LayoutTests/editing/spelling/spelling-marker-description.html » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

Index: LayoutTests/editing/spelling/spelling-huge-text-expected.txt

diff --git a/LayoutTests/editing/spelling/spelling-huge-text-expected.txt b/LayoutTests/editing/spelling/spelling-huge-text-expected.txt

index 859d9c0475b4d60723186c8d6fe6042083050e41..4f896a3c7c2c6cb8d50944f0acd98ac8d3f99ac5 100644

--- a/LayoutTests/editing/spelling/spelling-huge-text-expected.txt

+++ b/LayoutTests/editing/spelling/spelling-huge-text-expected.txt

@@ -3,7 +3,7 @@ Text to check is divided into chunks to make sure checking some huge text does n

On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".

-PASS internals.markerCountForNode(testEditable.childNodes[0], "spelling") is 6

+PASS internals.markerCountForNode(testEditable.childNodes[0], "spelling") became 6

PASS successfullyParsed is true

TEST COMPLETE