Comment #10 on issue 6755 by da...@chromium.org: Add back/forward
performance test
http://code.google.com/p/chromium/issues/detail?id=6755
To clarify, I think an integration test of the entire browser that does
something which
is sensitive to cache performance is a good idea. Smaller, more
Comment #6 on issue 6755 by patr...@chromium.org: Add back/forward
performance test
http://code.google.com/p/chromium/issues/detail?id=6755
To do this, the page-cycler framework will need some changes to allow it to
call
history.go. I think a clever way of going about it would be to increas
Comment #5 on issue 6755 by patr...@chromium.org: Add back/forward
performance test
http://code.google.com/p/chromium/issues/detail?id=6755
To do this, the page-cycler framework will need some changes to allow it to
call history.go. I think a clever way of going about it would be to
incre
Updates:
Labels: -Area-BrowserBackend Area-DevTools
Comment #1 on issue 6755 by patr...@chromium.org: Add back/forward
performance test
http://code.google.com/p/chromium/issues/detail?id=6755
(No comment was entered for this change.)
--
You received this message because you are listed
Status: Untriaged
Owner: patr...@chromium.org
Labels: Type-Other Pri-2 OS-All Area-BrowserBackend
New issue 6755 by patr...@chromium.org: Add back/forward performance test
http://code.google.com/p/chromium/issues/detail?id=6755
We should set up some automated performance tests that exercise
back
