A few days ago there was a post on the SproutCore Google Group by an individual asking if his code could be reviewed by people in the community. Given the request, I checked out the code from github and began to go through it. In a nutshell, I was reviewing a small SproutCore application that allows you to simply log in and log out of the application. The application makes use of Ki, a statechart framework, in order to keep track of what state the application is currently in. In addition, there are two custom views. One view represents a toolbar displaying whether you are logged in or logged out, and another view that represents a login form. The login form view also contains logic that will fake the log in procedure.
Well, it’s been a few weeks since I’ve had enough time to sit down at write another post, but here I am at it again. However, for my latest post, I’ve decided to write about a topic in SproutCore that sits outside of the more mainstream features of the framework: that is event simulation.
Now, now — hold on. I see you reaching for you mouse ready to checkout some other website, but hear me out on this topic. While event simulation in SproutCore isn’t really promoted much, it is useful to know. How? When you want to do test automation.