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
18/03/2006 • 6:47 pm 6
Update: Distributing media can be problematic. If you’ve read the comments below, I’m sure you agree that I’ve had my fair share of difficulties. There have been two issues that I’ve been struggling with recently; (a) the format that I was using (avi’s) only worked on some machines; and (b) the files were not always accessible.
To address the first problem, I’ve converted the orginal avi’s to mp4’s. I’ve tested the mp4’s under VLC and they play without any problems. The original avi’s still work with Windoze Media Player. The bad news is that neither format works with Quicktime. I’m inexperienced with QT and I’m out of options at this point. I’m open to suggestions on how to resolve this, if you have any.
To address the second problem, I’ve moved the files to a new (hopefully more reliable) host. The host also offers torrents, and that’s available as well. So, here are the screencasts:
Individual avi files:
Individual mp4 files:
Now, back to the original article …
My previous screencast [1] was a simple introduction to TDD with Ruby. The intention was to demonstrate TDD and not much else. Having done that there are a number of other topics that I feel need to be addressed including exceptions, database interaction and mocks.
In this screencast I’ve focused on TDD with exceptions and error handling.
Read the rest of this entry »
Filed under: Ruby, Screencasts, TDD, Test Driven Development
04/03/2006 • 6:45 pm 4
Update: This is part 1 of 2. You can find the second part of this series here.
Test Driven Development (TDD) is something that many people talk about but few actually do. A common misconception is that TDD is about writing acceptance tests before developing the code. It’s really more than automated acceptance tests … it’s about using unit tests to drive the development process.
There are several books ([1] and [2]), good written tuturials using java [3] and even a tutorial using Ruby [3]. But I find it’s very difficult to communicate how TDD should feel using the written word. In an attempt to help bridge the gap, I’ve created some screencasts that demonstrate TDD.
Read the rest of this entry »
Filed under: Ruby, Screencasts, TDD, Test Driven Development
Recent Comments