201
edits
SoftwareTesting: Difference between revisions
Jump to navigation
Jump to search
→Ideas to Collect
| Line 74: | Line 74: | ||
** can we use chrome urls (with appropriate manifest files) to access the jsunit core js files in a path-independent manner? this means we just have to worry about the test runner page and the test suite/case pages. | ** can we use chrome urls (with appropriate manifest files) to access the jsunit core js files in a path-independent manner? this means we just have to worry about the test runner page and the test suite/case pages. | ||
** this is only a problem for packaging jsunit-based tests in our tree so that they point to the same core jsunit files | ** this is only a problem for packaging jsunit-based tests in our tree so that they point to the same core jsunit files | ||
* 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 | |||