by Scott Becker
* Test Driven Development - What is it, why do it, what are the advantages?
* Future VMs will run JS faster, making "bigger", more processing intensive apps possible within a browser
* Traditionally web applications have most business logic running server side.
* Testing for server-side web applications has matured over the past few years
* This creates a growing need for testing at the browser level, but this area is still young and not as widely practiced
h3. What do we gain?
* Stable development - iterate without fear of breaking existing features
* Easier refactoring - rewrite the guts of your app and be confident it continues to work
* Speed - stop refreshing and clicking through your app to verify things are working, thats what computers are for
* Automation - repeatable tests help you do the right thing every time, without having to think about it
h3. Getting Started
* A simple example - a client-side form validation library and a suite of tests for verifying it works as expected
h3. Going further
* A complex example - integration testing, scripting user stories
* Testing across multiple browsers
* Incorporating JS tests into a larger development workflow with server-side tests
* Continous integration - running tests automatically, every time you commit
17th–19th June 2009