RESOLVED FIXED 60733
Port Mozilla's IndexedDB tests: indexes with keys and key ranges
https://bugs.webkit.org/show_bug.cgi?id=60733
Summary Port Mozilla's IndexedDB tests: indexes with keys and key ranges
Mark Pilgrim (Google)
Reported 2011-05-12 15:28:39 PDT
Original test: http://mxr.mozilla.org/mozilla2.0/source/dom/indexedDB/test/test_indexes.html?force=1 This is a port of a test from Mozilla's IndexedDB test suite. It creates an object store with several rows of data, creates indexes on each key, then iterates each index in a variety of ways (keys, key ranges, etc). Variations that WebKit fails have been split out into separate tests. This is what remains, which WebKit passes.
Attachments
Patch (93.32 KB, patch)
2011-05-12 15:35 PDT, Mark Pilgrim (Google)
no flags
Mark Pilgrim (Google)
Comment 1 2011-05-12 15:35:32 PDT
Tony Chang
Comment 2 2011-05-13 09:31:51 PDT
Comment on attachment 93358 [details] Patch I think this is fine, but a couple questions: - Are the results deterministic? It looks like multiple database queries get queued up. Will they always get resolved in the same order? - How long does this test take to run?
Mark Pilgrim (Google)
Comment 3 2011-05-13 09:53:38 PDT
In my testing the results are deterministic and nowhere near the timeout threshold. Less than one second on my poor old laptop.
Tony Chang
Comment 4 2011-05-13 12:12:55 PDT
Comment on attachment 93358 [details] Patch Ok, I suspect this is fine because queries always get answered in the order they come in. Ideally, tests should be only tens of ms, but under a second isn't terrible.
WebKit Commit Bot
Comment 5 2011-05-13 13:23:08 PDT
Comment on attachment 93358 [details] Patch Clearing flags on attachment: 93358 Committed r86457: <http://trac.webkit.org/changeset/86457>
WebKit Commit Bot
Comment 6 2011-05-13 13:23:14 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.