Sessions at Open Source Bridge 2009 about JavaScript on Thursday 18th June

So, you've made a Firefox add-on. You've modified web page content, or added a button to the toolbar. But where to go next? What APIs and technologies are available to help your application or add-on surprise and inspire? And once you've got a great idea, how can you make the implementation fast, responsive and respectful of system resource constraints?

I'll talk about tips, tricks and best practices for extending Firefox to the edge:

• Create multimedia extravaganzas with the audio, video and canvas tags
• Tight and polite integration of internet services into the browsing experience
• Writing lean and performant code
• Interacting with the host operating system
• Busting out of the browser with standalone applications

h2[=approaches]. Web Testing Approaches

Separating Concerns, Isolating Components
Unittesting vs Functional Testing
Full Monty (blurring the lines between unittesting and funcitonal testing)

h2[=toolsAndTech]. Tools and Technologies

Browserless tools (HTTP tools, Browser simulation, DOMless JavaScript Interpreters)
Browser tools (Watir, Selenium, Windmill)

h2[=writingTest]. Writing Windmill Tests

Starting Windmill
The Windmill IDE
Using the recorder
Adding actions and assertions
Using the Inspector
Serializing your test (Python vs JavaScript Tests)

h2[=debuggingTests]. Debugging Windmill Tests

Running tests
Debugging Failed Actions
Firebug and Firebug Lite
Using the Lookup object

h2[=runningTests]. Running Tests Continuously

Command Line Features
Hudson Plugin
Getting Windmill running in hosted environments like EC2

h2[=extra]. And now for something completely different

Dynamic testing (Windmill's eval APIs)
Testing Firefox Extensions (MozMill)