FrozenCanuck introduces Lebowski for the SproutCore framework. If you aren’t using automated testing to verify your app, you should be. If you claimed you couldn’t do it because you didn’t have any tools…well now you don’t have any excuses. Get to it!Tweet
You know how they say that the real world produces the best software. @frozencanuck, a member of the team here at @eloqua, has written an open source Ruby testing framework called Lebowski which leverages Selenium and is specifically designed for Sproutcore and it’s unique needs. Here is a [post](http://frozencanuck.wordpress.com/2010/06/08/introducing-lebowski-a-test-automation-framework-for-sproutcore/) where he talks about it in detail and you can find the repository for it [here](http://github.com/FrozenCanuck/Lebowski). It is still in development, but we are starting to use it in our big SproutCore application.
**…This is a guest post by Evin Grano (@etgryphon)**Tweet
If you’re trying to automate tests of your SproutCore application with Selenium, for example, you’ll realise that the HTML element ids are automatically generated. They change every now and then and break all your tests.
To get rid of this problem, you can override the
layerIdmethod of certain view classes to generate a stable, and human readable, id.
The following code takes the view hierarchy, and generates an id based on the parents’ names. For example, the
mainPage.mainView.someOtherView.theTargetViewview will be given the