Microsoft provides virtual machine disk images to facilitate website testing in multiple versions of IE, regardless of the host operating system. Unfortunately, setting these virtual machines up without Microsoft's VirtualPC can be extremely difficult. The ievms scripts aim to facilitate that process using VirtualBox on Linux or OS X. With a single command, you can have IE7, IE8 and IE9 running in separate virtual machines.

TAP, the Test Anything Protocol, is a simple text-based interface between testing modules in a test harness. TAP started life as part of the test harness for Perl but now has implementations in C, C++, Python, PHP, Perl, Java and others.
Here's what a TAP test stream looks like:
1..4
ok 1 - Input file opened
not ok 2 - First line of the input valid
ok 3 - Read the rest of the file
not ok 4 - Summarized correctly # TODO Not written yet

In comments, Steve Freeman writes: "+1 Our phrase for this is "Stub Queries, Expect Actions", where an action changes the environment outside the object under test and a query doesn't. In your example, finding is a query, so it should be stubbed. In jMock, that would be an "allowance". Of course it's the same machinery under the covers, but it's about expressing the intent of the test."

Apparently that whole "bootxp/xplite/etc" thing is an entire category of software now. Who knew?

Autotest-enabled Ruby Koans fork.

"How it works
Write a question with 2 options.
Pay us - just $5.00.
Get answers from 50 people - with demographics and comments!"

New automated-browser-testing-kid on the block.

Grease Your Suite

Tips and tricks for faster testing

Nick Gauthier

SmartLogic Solutions

"45 minutes: do a bit of programming. A simple problem will be presented. Attendees solve it working in pairs, with the navigator VERY strictly enforcing this micro-process:
1) write exactly ONE failing test
2) make the test from (1) pass by first writing implementation code IN THE TEST
3) create a new implementation method/function by:
3.1) doing extract method on implementation code created as per (2), or
3.2) moving implementation code as per (2) into an existing implementation method
4) only ever create new methods IN THE TEST CLASS
5) only ever create implementation classes to provide a destination for extracting a method created as per (4).
6) populate implementation classes by doing move method from a test class into them
7) refactor as required
8) go to (1) "

"We’re currently adding Facebook integration to an existing application that uses Authlogic. That means adding a button that any user can press on the login form that then takes them to Facebook, signs them in and then lets them log into our site. For this purpose and the time being “Facebook integration” means only that: letting the user login with their Facebook details. For the Facebook side of things we’re using Facebooker which is not the well-documented library we all would hope it is. Oh, and you cannot use it as a gem with Rails."

"web2py provides a solution for this problem and includes a minimalist Bayesian classifier trained and adapted to the scope.
...
Of course the text does not make any sense. That is a feature."

Here’s the 5 second version:
1. Bring a laptop to a bar
2. Offer to buy someone a beer in exchange for participating in a user study
3. Watch your application crash & burn as people do all sorts of ridiculous ass shit they would never do in a lab but constantly do in real life
4. Go back, apply the lessons you have learnt, repeat until you have an app that is 100% drunk person proof