Asa Dotzler wrote:
> Debug|chofmann's browser buster.
http://komodo.mozilla.org/buster/
for those of you who don't have nightly builds. This page should work in (almost)
any/all js enabled browsers.
Randall Parker wrote:
> Is there any kind of browser buster that would navigate different browsers
> from different vendors in order to generate comparative data on stability?
chofmann's test w/ time readings would probably work. you might need some minor
modifications because chofmann's buster doesn't wait for pages to complete loading...
> I wonder if IE is scriptable to be controlled to go to a series of sites.
certainly.
> Running Moz and IE side by side with a scripted series of sites would yield
> some useful data.
how can you say this w/o trying?
> But since IE's performance couldn't be reported back by
> talkback we'd need another way to report back the results.
it's pretty easy to tack an app into the system that counts crashes by program. dr
watson can do this.
> 1) How does the chofmann's existing browser buster choose the series of links
> that it visits?
it's random based on the category you select. -- read the source.
> 2) Is there some list of the top n hundred sites visited? Or top n pages in
> those sites that are stable URLs that get visited?
if you read the page about browser buster you wouldn't have needed to ask this
question.
> 3) Would it make sense to have a page scanner that would go to big sites and
> then link to some links off of them and then send the two browsers to these
> links in succession?
who knows. try it and see
> 4) I think the main testing program should try to load each page itself
> before telling each of the browsers to do so. Once it succeeded then it would
> direct each browser to load a page.
bah. then you'd miss behaviors of server not found and such, which you should
experience _in_ the browser.
> 5) Can a separate process tell Moz to go to a page? (preferably without
> telling Moz to open a new window but it'd be nice to test with multiple
> windows opening as well)
on windows DDE can do this (for moz, ns4, ie, and probably most other browsers)
> 6) Can Moz use IPC to report back that it finished loading a given page?
whose ipc do you speak of? x-remote is an ipc, but iirc it currently doesn't return
useful responses. DDE is another, i'm not sure if you can or are expected to return
responses. mozilla has a few other rpc mechanisms, but most aren't used for what you
want.
> I think a tool to compare browsers would need to run as a separate process
> that did not crash when a browser crashed. So hence the need for some form of
> IPC via perhaps a named pipe or a socket connection to the browser.
sounds like you're a unix/linux user. i believe you might be right but that your
reasons are wrong. learn about total recall (mozdev.org) and consider a silly shell
script that respawns mozilla when it quits.
as stated earlier we have x-remote and dde. feel free to work to improve x-remote
(talk to [EMAIL PROTECTED])
