Find out about one of the cool new features that will be offered by Q2 2013 of Telerik OpenAccess ORM - automatic generation of Data Annotation attributes.
Wondering what's next with Test Studio? We've given you some ideas of what's planned, and over the next few weeks we'll be giving you some chances to peek through the curtain. For starters... disclaimer: this is still a work in progress; this screenshot may or may not accurately reflect the final product as it will ship. About the Author Steven Vore Steven Vore
is an Evangelist for Telerik's Test Studio.
He has worked in software support and testing for the better part of two decades, and enjoys exploring ways to make software easier to use.
He is a fan of ...
I frequently see teams new to test automation making a number of common mistakes. One of those is adding in unnecessary verifications. Verifications are obviously a critical piece of good tests—it’s validating the system is working as we expect for that particular test case. Where new automation crews get confused is whether to add explicit verifications when navigating through their application, or after an explicit wait has been used to handle an asynchronous operation like an AJAX call or some JavaScriptish operation on the local browser UI. (The same concepts work for XAML or mobile applications!) Avoid Verifying Navigation Let’s ...
Batch editing is a new type of inline editing which brings the editing experience of RadGrid closer to this of Excel. Upon a click/double-click (whatever the developer specifies), the user will be able to open the cell for editing and edit as many cells as they like. By hitting the Save button just once, all their changes will be preserved.
Routers are powerful tools in Single Page Applications, and Kendo UI's
router provides an API to wrap up this power.
But the API hides a lot of potential complexity and performance
issues if you're not careful. Calling the navigate method
without regard for the current context of the application and whether
or not that context is changing can result in unwanted re-rendering
of the entire application. This can reduce the responsiveness of the
app, waste time re-drawing content that isn't changing, and cause a
lot of flickering on the screen - and none of this is desirable
from a user's perspective.
This is Part 3 of a four part series where we explore some of the tools available to detect and manage online/offline connectivity in web/mobile applications. In Part 1 we looked at the available APIs for detecting connectivity state (and the woes associated with them). In Part 2 we wrote a hand-rolled abstraction to manage using these APIs together and began to see elements of a state machine emerge from the chaos. In this post we're going to drive the state machine stake deeper by exploring how we can keep our FSMs from violating SRP, and set the stage for using multiple FSMs together to model more complex application behavior.