mirror of
https://github.com/servo/servo.git
synced 2025-08-15 02:15:33 +01:00
Fix IndexedDB WPT coverage (#37607)
The settings for WPT IndexedDB coverage is incorrect. We never ran the IndexedDB tests actually. Testing: `tests/wpt/tests/IndexedDB` --------- Signed-off-by: Wu Yu Wei <yuweiwu@pm.me> Signed-off-by: Josh Matthews <josh@joshmatthews.net> Co-authored-by: Josh Matthews <josh@joshmatthews.net>
This commit is contained in:
parent
476b05676f
commit
25fe003af2
230 changed files with 7240 additions and 38 deletions
74
tests/wpt/meta/IndexedDB/idb-explicit-commit.any.js.ini
vendored
Normal file
74
tests/wpt/meta/IndexedDB/idb-explicit-commit.any.js.ini
vendored
Normal file
|
@ -0,0 +1,74 @@
|
|||
[idb-explicit-commit.any.worker.html]
|
||||
[Explicitly committed data can be read back out.]
|
||||
expected: FAIL
|
||||
|
||||
[commit() on a version change transaction does not cause errors.]
|
||||
expected: FAIL
|
||||
|
||||
[A committed transaction becomes inactive immediately.]
|
||||
expected: FAIL
|
||||
|
||||
[A committed transaction is inactive in future request callbacks.]
|
||||
expected: FAIL
|
||||
|
||||
[Puts issued after commit are not fulfilled.]
|
||||
expected: FAIL
|
||||
|
||||
[Calling commit on an aborted transaction throws.]
|
||||
expected: FAIL
|
||||
|
||||
[Calling commit on a committed transaction throws.]
|
||||
expected: FAIL
|
||||
|
||||
[Calling abort on a committed transaction throws and does not prevent persisting the data.]
|
||||
expected: FAIL
|
||||
|
||||
[Calling txn.commit() when txn is inactive should throw.]
|
||||
expected: FAIL
|
||||
|
||||
[Transactions with same scope should stay in program order, even if one calls commit.]
|
||||
expected: FAIL
|
||||
|
||||
[Transactions that explicitly commit and have errors should abort.]
|
||||
expected: FAIL
|
||||
|
||||
[Transactions that handle all errors properly should behave as expected when an explicit commit is called in an onerror handler.]
|
||||
expected: FAIL
|
||||
|
||||
|
||||
[idb-explicit-commit.any.html]
|
||||
[Explicitly committed data can be read back out.]
|
||||
expected: FAIL
|
||||
|
||||
[commit() on a version change transaction does not cause errors.]
|
||||
expected: FAIL
|
||||
|
||||
[A committed transaction becomes inactive immediately.]
|
||||
expected: FAIL
|
||||
|
||||
[A committed transaction is inactive in future request callbacks.]
|
||||
expected: FAIL
|
||||
|
||||
[Puts issued after commit are not fulfilled.]
|
||||
expected: FAIL
|
||||
|
||||
[Calling commit on an aborted transaction throws.]
|
||||
expected: FAIL
|
||||
|
||||
[Calling commit on a committed transaction throws.]
|
||||
expected: FAIL
|
||||
|
||||
[Calling abort on a committed transaction throws and does not prevent persisting the data.]
|
||||
expected: FAIL
|
||||
|
||||
[Calling txn.commit() when txn is inactive should throw.]
|
||||
expected: FAIL
|
||||
|
||||
[Transactions with same scope should stay in program order, even if one calls commit.]
|
||||
expected: FAIL
|
||||
|
||||
[Transactions that explicitly commit and have errors should abort.]
|
||||
expected: FAIL
|
||||
|
||||
[Transactions that handle all errors properly should behave as expected when an explicit commit is called in an onerror handler.]
|
||||
expected: FAIL
|
Loading…
Add table
Add a link
Reference in a new issue