Wilhelm: how I should run it? How
do I know if I'm getting the proper results?

Kai: it starts with the highest
test; if that doesn't work, you go to lowest
... and then you go to middle steps
... one pb is that if you start too high, you may crash the
browser
... on my nokia device, I tried that, crashed the browser, and
the memory wasn't cleared

<Zakim> dom, you wanted to
ask what 'what doesn't work' mean?

Kai: when it works, it gives you
a message "server limit exceeded" or something like that
... user agents with good memory capabilities can reach
that
... it's roughly for 2 Mo of data

Dom: maybe we could have
something more user friendly than "server limit exceeded" :)
?
... if we want to further advertise that test

Kai: could this be brought to
another server to reduce the load on my server?

Kai: it was the easiest way of
doing it :)
... I could probably be doing it more efficiently
... but in any case, this is likely to create load on whatever
server hosts it
... code is written in shell, should be fairly easy to
read
... Apprently, IE Mobile can't go over 1MB

Rechartering

Report from AWTA 2009

Wilhelm: small but active
conference, with 25 participants
... around the Watir framework that can be used to automate
browser testing
... originally built for IE around COM components
... can be used to make browsers do anything
... various people are working on extending this to other
browsers
... we made a presentation on our Opera implementation
... can be done on any opera device
... it's made for being used over the wire
... There was discussions on the different frameworks
used
... and how web applications testers did their testing
... I think it's an important community to keep an eye on
... cross-browsers support for this could permit automate
testing for web standards conformance

dom: were there other browser
vendors?

Wilhelm: nope, but someone has
implemented it for Safari through Applescript
... I think there is official support from the Chrome Team

Dom: any opportunity for getting
other browsers to join that effort?

Wilhelm: no official support for
IE, but it "just works"
... the firewatir implementation for firefox is not officially
supported by Mozilla, but the extension mechanism allows to do
it fairly simply

dom: but is there any need to
help there, or is just a matter of letting the community
provide whatever is needed?

wilhelm: running code is mostly
what's needed at this point
... getting browser vendors to support this officially would be
great, but isn't strictly required

kai: was there any talk about
pocket IE?

Wilhelm: no, it wasn't
... not sure what APIs they expose

Kai: I think it should be
easy

Wilhelm: our implementations has
3 parts: the opera binary, to which you can communicate through
a documented protocol, a proxy that connects to the binary, and
tests scripts based
... we're adding support for Watir in our tests scripts