diff options
| author | jorlow@chromium.org <jorlow@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-08-05 06:02:07 +0000 |
|---|---|---|
| committer | jorlow@chromium.org <jorlow@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-08-05 06:02:07 +0000 |
| commit | 6d3744980e419303b01f12fe6c82ff81cfc2fd2f (patch) | |
| tree | 3ad6ece5678bf4cf53fb04d232dfb779ccf4b89f /o3d/samples/debugging.html | |
| parent | aded0071867946f9aab08ce88ebbfd83c77c83af (diff) | |
| download | chromium_src-6d3744980e419303b01f12fe6c82ff81cfc2fd2f.zip chromium_src-6d3744980e419303b01f12fe6c82ff81cfc2fd2f.tar.gz chromium_src-6d3744980e419303b01f12fe6c82ff81cfc2fd2f.tar.bz2 | |
Run the DOM Storage layout tests in the UI test framework since the test shell doesn't hit very much of the new code. I still plan to write unit tests and we're still goign to enable the layout tests in test shell, but this is still a good way for us to test the full stack ASAP.
Workers has used this technique for a while now. This CL factors out the layout test running code from the workers ui test and moves arounds directories a bit so not everything is in the "workers" directory.
Doing this via a v8 extension is the right way to go long term, but I ran into a couple snags, so I think this is a good first step.
TEST=none
BUG=none
Review URL: http://codereview.chromium.org/159720
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@22466 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'o3d/samples/debugging.html')
0 files changed, 0 insertions, 0 deletions