Web testing

Содержательный блог, интересная (мне: раз, два) статья, про тестирование веб-приложений:

Problem in general with web testing is that you cannot unittest it, it’s always a functional test. ...

What are the tools for web application testing?

Broadly two categories:

Browserless Tools

* Raw HTTP tools

* Browser Simulation Tools

* JavaScript interpreters (but problem is e.g. that a DOM implementation is on spec and does not look like a browser)

Browser Tools

* Selenium

* Windmill (own rewrite because of problems with Selenium)

* Watir (takes a different approach: implements a trusted module in IE/Firefox etc.)

Tools are not really comparable. He showed nevertheless some example comparison:

* Windmill and Selenium supports all major browsers with one product, Watir needs different libraries

* Test recorder works on every browser for Windmill and Watir, with Selenium only with trusted FF plugin

* All three work cross domain and support SSL

* Windmill supports Python, JavaScript, Ruby. Selenium many, Watir just Ruby.

* Integrated Debugging Tools: Firebug, FB Lite and Inspector for Windmill. Selenium has no tools, as well as Watir

* Proxy Manipulation: There in Windmill but could be better, not there in Selenium, Watir does not use a proxy. What that means is that you can control what will come through the proxy and manipulate requests etc.

mrtopf.de/blog/python_zope/europython-2009-web-testing-with-windmill

А комплексного решения как не было, так и нет. Может, надо в спецификации браузеров добавить главу, посвященную тестированию? Чтобы, согласно стандарту, любой браузер поддерживал скрипты тестирования веб-приложений?