Bug 15609
| Summary: | testkjs should made long-running to speed up run-javascriptcore-tests | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Eric Seidel (no email) <eric> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | ||
| Priority: | P2 | ||
| Version: | 523.x (Safari 3) | ||
| Hardware: | Mac | ||
| OS: | OS X 10.4 | ||
Eric Seidel (no email)
testkjs should made long-running to speed up run-javascriptcore-tests
DumpRenderTree has a "long running" option, where it will stay launched and sit and wait for new data to come in and run it. testkjs could benefit from such as well. I expect it would *drastically* reduce how long it takes to run run-javascriptcore-tests (which is currently a ridiculously long time).
testkjs would need to make a new global object for each test, but would want to keep around certain files in memory (the shell files) and just run those before any test it's given. A simple LRU cache of recently read-from-disk js files would probably do the trick.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |