Command recording and replaying module for Python. Useful for building a test harness to simulate a missing component (allowing you to build and test top-down instead of bottom up).

Quoted: Selenium is a test tool for web applications. Selenium tests run directly in a browser, just like real users do.

An interesting scripting language for automating web browsing tasks. Could be really good for unit testing web UI as well as stress testing a web site.

The most prime marketing space at Google - The Toilet!

Quoted: It sounds obvious, but people work better when they’re involved in something they’re passionate about.

Google has an A/B testing tool that will also help you analyze experiments with multi-variable changes all being made at once.

Quoted: NUnit 2.0 is an excellent example of idiomatic design. Most folks who port xUnit just transliterate the Smalltalk or Java version. That's what we did with NUnit at first, too. This new version is NUnit as it would have been done had it been done in C# to begin with.

I'm open-sourcing a unit testing library I've developed for Javascript.

Jaybe introduced me to the Visual Studio Unit testing and "Test Driven Development" methodology. I can't say I agree with every aspect of TDD when carried to the extreme but there are some parts I like a lot:

- Write (failing) unit tests BEFORE writing your code. (But I think you do need to do some design work and object modeling before you can start the unit testing).
- Use code coverage to make sure you're getting very high % coverage of all your code before considering your tests complete.

Part I'm not so keen on is writing code that is a "stub" for the actual working system. It seems to me this leads to a lot of writing and re-writing of code that is going to get thrown away. If you're going to write the "minimum implementation" for getting your unit tests to pass, I still think this needs to be mostly NOT throw-away code. Otherwise, how is this making "progress"?

Quoted: The purpose of this project is to build some insightful and practical guidance around using Visual Studio Team System 2005. It's a collaborative effort between patterns & practices, VSTS team members, and industry experts.

This is a good post on some of the possible hang-ups with A/B testing. Take-aways:

- Understand segmentation of users (new vs. repeat)
- Change one thing at a time (or use MVT analysis)