201
edits
SoftwareTesting:Tools:SimpleXulTestHarness: Difference between revisions
Jump to navigation
Jump to search
SoftwareTesting:Tools:SimpleXulTestHarness (view source)
Revision as of 18:04, 15 September 2006
, 15 September 2006no edit summary
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
** need to add result reporting (pass/fail) to this example | ** need to add result reporting (pass/fail) to this example | ||
= description = | = description = | ||
davel used this set of scripts to help verify that the default search engine plugins bundled with localised builds of firefox were as expected. | |||
The wrapper script extract_search.sh expects paths to firefox dmg files on the command line. It installs firefox from each dmg, creates a new profile, runs the "test" to list the search engine stuff, then deletes the profile and that instance of firefox. | |||
The wrapper script has the following assumptions: | |||
* running on a mac | |||
* APP_DATA_DIR set to ~/Library/Application Support/Firefox | |||
** on my machine, I have a symlink to that dir from my home dir | |||
* SEARCHTEST_DIR set to directory containing all these files | |||
* WORK_DIR set to a writable directory, use to install firefox and hold the newly-created profile | |||
* tests.manifest contains a file: url link to the SEARCHTEST_DIR directory | |||
** hmm, we could make extract_search.sh edit the manifest file on the fly . . . | |||
* nothing is creating or deleting profiles while this script is running | |||
** changes to profiles.ini made by other things while this script is running will be clobbered. | |||
= to do list = | = to do list = | ||
* figure out where/how to check this in to the tree | * figure out where/how to check this in to the tree | ||