SoftwareTesting:Tools:SimpleXulTestHarness: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
= description = | = description = | ||
= to do list = | = to do list = | ||
* figure out where/how to check this in to the tree | |||
** as an extension, to populate chrome://tests/ ? | |||
** how can test stuff from other parts of the tree get installed into chrome://tests/ | |||
* add invocation hooks | |||
** what test to run | |||
** auto-discovery of tests? | |||
** command -line pointer to test manifest file, like layout reftest? | |||
* add test result reporting | |||
** simple dump statements | |||
** maybe a chrome test runner with progress bar, like jsunit's test runner | |||
Revision as of 17:44, 15 September 2006
old content
- example xul/run-js-as-chrome test (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
- in the example, extract_search.sh demonstrates how to create a profile
description
to do list
- figure out where/how to check this in to the tree
- as an extension, to populate chrome://tests/ ?
- how can test stuff from other parts of the tree get installed into chrome://tests/
- add invocation hooks
- what test to run
- auto-discovery of tests?
- command -line pointer to test manifest file, like layout reftest?
- add test result reporting
- simple dump statements
- maybe a chrome test runner with progress bar, like jsunit's test runner