mirror of
https://gitlab.winehq.org/wine/wine-gecko.git
synced 2024-09-13 09:24:08 -07:00
| .. | ||
| head_queries.js | ||
| readme.txt | ||
| stub-test.js | ||
| test_415716.js | ||
| test_abstime-annotation-domain.js | ||
| test_abstime-annotation-uri.js | ||
| test_containersQueries_sorting.js | ||
| test_excludeReadOnlyFolders.js | ||
| test_onlyBookmarked.js | ||
| test_querySerialization.js | ||
| test_redirectsMode.js | ||
| test_results-as-tag-contents-query.js | ||
| test_results-as-visit.js | ||
| test_searchterms-domain.js | ||
| test_searchterms-uri.js | ||
| test_sorting.js | ||
| test_tags.js | ||
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.