Your current filters are…
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
Many software projects suffer from long release schedules, feature freezes, painful QA processes, awkward merges, version number debates, backwards compatibility paralysis -- oh, and customers who aren't completely delighted.
Project management doesn't have to be this way.
Several real-world projects have solved these problems with a combination of iteration, refactoring, continual improvement, reflection, and low-ceremony processes. The solutions aren't all simple or easy, but they're easy to understand, and they're within your grasp. This talk will tell you what's possible and recommend concrete steps to improve your project management.
17th–19th June 2009