toolkit/components/places/tests/queries/readme.txt

Sat, 03 Jan 2015 20:18:00 +0100

author
Michael Schloh von Bennewitz <michael@schloh.com>
date
Sat, 03 Jan 2015 20:18:00 +0100
branch
TOR_BUG_3246
changeset 7
129ffea94266
permissions
-rw-r--r--

Conditionally enable double key logic according to:
private browsing mode or privacy.thirdparty.isolate preference and
implement in GetCookieStringCommon and FindCookie where it counts...
With some reservations of how to convince FindCookie users to test
condition and pass a nullptr when disabling double key logic.

michael@0 1 These are tests specific to the Places Query API.
michael@0 2
michael@0 3 We are tracking the coverage of these tests here:
michael@0 4 http://wiki.mozilla.org/QA/TDAI/Projects/Places_Tests
michael@0 5
michael@0 6 When creating one of these tests, you need to update those tables so that we
michael@0 7 know how well our test coverage is of this area. Furthermore, when adding tests
michael@0 8 ensure to cover live update (changing the query set) by performing the following
michael@0 9 operations on the query set you get after running the query:
michael@0 10 * Adding a new item to the query set
michael@0 11 * Updating an existing item so that it matches the query set
michael@0 12 * Change an existing item so that it does not match the query set
michael@0 13 * Do multiple of the above inside an Update Batch transaction.
michael@0 14 * Try these transactions in different orders.
michael@0 15
michael@0 16 Use the stub test to help you create a test with the proper structure.

mercurial