> -- More generally, the biggest problem I have with Quixote is that that
> I have with all web dev't -- the compile/run/edit cycle is lengthened
> too much by the need to work with the browser (forget cookies, etc.).  I
> think some adjunct tools that helped with  that would increase
> productivity a lot.  Not sure what that means yet =).  I suppose what I
> really want is a deeply scriptable browser.

And if you are using persistent processes, you constantly have to restart
the process, refresh cookies, etc.

To help with the restarting, I've been using a subclass of SessionPublisher
that sets self.exit_now if source files have changed.

To help with the browser awkwardness, I have a cmdline tool that fakes up cgi
requests, and a few functions for unit testing that fakes up an HTTPRequest.
User readable output is provided by 'w3m -dump', and tests simply look for key
substrings in there.

It works ok, but I haven't used it long enough to decide if it's really less
work than all the browser reloading.  Writing tests is always more work in the
short term than just testing by hand.

I'm sure you work up a scheme that calls w3m -dump or lynx or whatever on
remote urls, and then send a series of requests and expect certain responses,
to truly simulate the browser requests.