third_party/WebKit/LayoutTests/storage/indexeddb/lazy-index-population-expected.txt - Issue 1362953003: Fire window.onerror for uncaught IndexedDB errors

Unified Diff: third_party/WebKit/LayoutTests/storage/indexeddb/lazy-index-population-expected.txt

Issue 1362953003: Fire window.onerror for uncaught IndexedDB errors (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master

Patch Set: Rebased Created 3 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 | « third_party/WebKit/LayoutTests/storage/indexeddb/lazy-index-population.html ('k') | third_party/WebKit/LayoutTests/storage/indexeddb/request-event-propagation-expected.txt » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

Index: third_party/WebKit/LayoutTests/storage/indexeddb/lazy-index-population-expected.txt

diff --git a/third_party/WebKit/LayoutTests/storage/indexeddb/lazy-index-population-expected.txt b/third_party/WebKit/LayoutTests/storage/indexeddb/lazy-index-population-expected.txt

index e78a4e61684e39abd3279013acb0330172156108..7f795295a7169862a3a33b0d0ae061daf32153c4 100644

--- a/third_party/WebKit/LayoutTests/storage/indexeddb/lazy-index-population-expected.txt

+++ b/third_party/WebKit/LayoutTests/storage/indexeddb/lazy-index-population-expected.txt

@@ -1,3 +1,6 @@

+CONSOLE ERROR: line 1: ConstraintError: Unable to add key to index 'index1': at least one key does not satisfy the uniqueness requirements.

+CONSOLE ERROR: line 1: ConstraintError: Unable to add key to index 'index2': at least one key does not satisfy the uniqueness requirements.

+CONSOLE ERROR: line 1: ConstraintError: Unable to add key to index 'index4': at least one key does not satisfy the uniqueness requirements.

Verify edge cases that lazy index population in an IndexedDB implementation might reveal.

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

@@ -19,8 +22,10 @@ request1 received success event

PASS ++state is 1

request2 received error event

PASS ++state is 2

-transaction aborted

+PASS Got expected error: 'ConstraintError: Unable to add key to index 'index1': at least one key does not satisfy the uniqueness requirements.'

PASS ++state is 3

+transaction aborted

+PASS ++state is 4

PASS trans.error.name is 'ConstraintError'

Verify that uniqueness constraints are enforced when index is created before puts:

@@ -37,8 +42,10 @@ request1 (index2) received success event

PASS ++state is 1

request2 (index2) received error event

PASS ++state is 2

-transaction aborted

+PASS Got expected error: 'ConstraintError: Unable to add key to index 'index2': at least one key does not satisfy the uniqueness requirements.'

PASS ++state is 3

+transaction aborted

+PASS ++state is 4

PASS trans.error.name is 'ConstraintError'

Verify that uniqueness constraints are enforced when index is created after puts:

@@ -71,8 +78,10 @@ request1 received success event

PASS ++state is 1

request2 received error event

PASS ++state is 2

-transaction aborted

+PASS Got expected error: 'ConstraintError: Unable to add key to index 'index4': at least one key does not satisfy the uniqueness requirements.'

PASS ++state is 3

+transaction aborted

+PASS ++state is 4

PASS trans.error.name is 'ConstraintError'

PASS successfullyParsed is true