SoftwareTesting:Tools:SimpleXulTestHarness: Difference between revisions

Jump to navigation Jump to search
checkpoint
No edit summary
(checkpoint)
Line 1: Line 1:
= old content =
* example xul/run-js-as-chrome test ([http://people.mozilla.com/~davel/scripts/ davel's example])
** in the example, extract_search.sh demonstrates how to create a profile
*** 2 steps - CreateProfile makes the directory and prefs.js file, and the first run populates the profile directory with all the other stuff
** the sleep 5 is necessary because firefox (on mac at least) restarts itself during the first-run process.  probably extension manager checking for stuff
** installing an extension is not covered by 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.
davel used this set of scripts to help verify that the default search engine plugins bundled with localised builds of firefox were as expected.
Line 22: Line 15:
** changes to profiles.ini made by other things while this script is running will be clobbered.
** changes to profiles.ini made by other things while this script is running will be clobbered.


= how to run =
# download contents of [http://people.mozilla.com/~davel/scripts/ this directory] to a directory on your mac
# edit extract_search.sh and tests.manifest, replacing paths with the ones on your machine
# download firefox .dmg files you want to "test"
# invoke extract_search.sh
==example==
  <code>./extract_search.sh "en-US/Firefox 1.5.0.7.dmg" "en-GB/Firefox 1.5.0.7.dmg"</code>
== output from above example ==
 
= comments =
* in the example, extract_search.sh demonstrates how to create a profile
** 2 steps - CreateProfile makes the directory and prefs.js file, and the first run populates the profile directory with all the other stuff
* the sleep 5 is necessary because firefox (on mac at least) restarts itself during the first-run process.  probably extension manager checking for stuff
* installing an extension is not covered by this example
= 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
Line 33: Line 41:
** simple dump statements
** simple dump statements
** maybe a chrome test runner with progress bar, like jsunit's test runner
** maybe a chrome test runner with progress bar, like jsunit's test runner
* make this work for already-installed firefox
* make this work on windows and linux
201

edits

Navigation menu