12/08/2006 • 10:12 pm 0
Selenium [1] is a nice tool for testing browser based user interfaces. It’s simple to install and with the firefox IDE plugin, it’s even easier to use. But there are some tests that are just not accessible through a UI. Should you even test functionality that’s not immediately expressed, and if so how?
Read the rest of this entry »
Filed under: Patterns, Selenium, TDD, Test Driven Development
23/04/2006 • 12:23 am 1
Update: WordPress has altered how the code tags function, making this post very confusing and difficult to read. I’ve replace the code tags and so, even though it’s not pretty, it’s at least readable.
My current client is working with Selenium to automate their acceptance testing. Selenium is an open source tool javascript framework for testing web applications. From the OpenQA website [1]:
"Selenium uses a unique mechanism which allows it to run on multiple platforms. Installed with your application webserver, Selenium automatically deploys its JavaScript automation engine — the Browser Bot — to your browser when you point it at the Selenium install point on your webserver. Thus, you must have write access to the machine your web application server is running on to install Selenium."
-OpenQA.Org
Filed under: Selenium, TDD, Technology, Test Driven Development
Recent Comments