So, ya. This post is kind of overdue, but in any case, a few weeks ago I gave a talk on my Lebowski framework at the San Francisco Selenium Meetup group. The good folks over at Sauce Labs recorded my presentation, which means that even if you weren’t able to attend you can still watch my presentation online. Oh, and also a big thanks to everyone who came out that night! My talk was up against some bad weather and the Giants game, and as I learned, San Franciscans love their Giants. Also thanks to the good folks over at Twitter for hosting the event at their headquarters! The Twitter peeps definitely have an awesome location and one kick-ass eating quarters.
Just as a quick summary, my presentation focused on what Lebowski is, the framework’s architecture, and how you use Lebowski to test your SproutCore application.
The first ten minutes or so is an introduction that tries to establish the difference between what a traditional web application is and a web application built using SproutCore. By understanding the differences between the two it helps provide a reason as to why you would use a framework like Selenium to test a traditional web app versus using Lebowski to test a SproutCore app.
The second part of the talk focuses on the architecture. Lebowski follows a proxy architecture where you use proxies within a script (a “Lebowski” script) to communicate with SproutCore objects that are loaded within the web browser. For anyone who uses Lebowski, the main focus is to create proxies that are specific to your application and write scripts that make use of those proxies and the proxies that come stock with the Lebowski framework.
The final part of the talk covers how to use Lebowski. I start off simple with a Hello World introduction that goes over the basics of how a SproutCore application is built and how to test it. The second code example goes over some of the more advanced proxies that come with the famework: the list view proxy and the palette pane proxy.
Basically what I want you to take away from the presentation is that Lebowski was built to be easy to use and helps facilitate proper communication between those who write SproutCore apps and those who test it. Although you have to know some stuff about SproutCore, you don’t have to be a SproutCore expert; just enough to get you by.