While it's having no impact on performance or anything, it's becoming increasingly difficult to keep track of where tests belong & where to put new ones. So some ideas: * Structured file naming scheme (e.g. test_mozStorage_api_findLogins.js). Also to think about is bug # specific, or problems like the base 64 issue, where it's not a specific API that's being tested. * Shared or resuable fixtures - At the top of each test_X file, there are usually a number of fixtures that are loaded; sometimes there are more loaded later in a test file. Some are specific to particular tests, others are more general, many correspond to values stored in the data files. Simplifying this would be good too.
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.