gecko-dev/toolkit/components/places/tests/queries
2009-05-04 20:40:34 -07:00
..
head_queries.js Bug 488783 - Tags list no longer sorted (alphabetized) in latest Shiretoko nightly, r=dietrich a=blocking191 2009-04-22 14:22:53 +02:00
readme.txt
stub-test.js
tail_queries.js
test_abstime-annotation-domain.js
test_abstime-annotation-uri.js
test_containersQueries_sorting.js Bug 488783 - Tags list no longer sorted (alphabetized) in latest Shiretoko nightly, r=dietrich a=blocking191 2009-04-22 14:22:53 +02:00
test_onlyBookmarked.js Bug 444179 - Library>Views>Sort>Sort by Tags does nothing, r=mak77 2009-01-30 13:34:38 +01:00
test_querySerialization.js Bug 399799 - Provide better options to query for tags (r=dietrich) 2009-05-04 20:40:34 -07:00
test_redirectsMode.js Bug 487777 - History menu is slow and takes ages to open, trunk version, r=dietrich 2009-04-18 14:12:06 +02:00
test_searchterms-uri.js
test_sorting.js Bug 444179 - Library>Views>Sort>Sort by Tags does nothing, r=mak77 2009-01-30 13:34:38 +01:00
test_tags.js Bug 399799 - Provide better options to query for tags (r=dietrich) 2009-05-04 20:40:34 -07:00

These are tests specific to the Places Query API.

We are tracking the coverage of these tests here:
http://wiki.mozilla.org/QA/TDAI/Projects/Places_Tests

When creating one of these tests, you need to update those tables so that we
know how well our test coverage is of this area.  Furthermore, when adding tests
ensure to cover live update (changing the query set) by performing the following
operations on the query set you get after running the query:
* Adding a new item to the query set
* Updating an existing item so that it matches the query set
* Change an existing item so that it does not match the query set
* Do multiple of the above inside an Update Batch transaction.
* Try these transactions in different orders.

Use the stub test to help you create a test with the proper structure.