If you were following Twitter last this last weekend (4 and 5 May) you may have seen a number of Tweets tagged with #TelSum. That was the Telerik Testing Summit, a peer conference held in Austin, Texas. Telerik welcomed a number of thought leaders in the testing and software industry to Austin, Texas, for two days of discussions on the state of software development. More importantly, we as a group were focused on what we could do to try and improve things. Telerik was represented by myself and Phil Sams, plus Holly Bertoncini, our event organizer. Joining us ...

Taking a Step Back – What is Accessibility? Accessibility is always  a large concern when creating applications. Whether these are meant for the web, desktop machines, or even mobile devices, accessibility is a huge factor. I have often run into scenarios where developers are not even aware of accessibility concerns, or decide to leave it as one of those “oh, I’ll get to it later” tasks on their TODO list. Some of you might even be asking yourself what accessibility actually is. Well, when I talk about accessibility I’m referring to the ability for your application to function for people with...

A good test case is neither too small nor too big. A good test case stands alone, sets up pre-test conditions, exercises the application under test (AUT), verifies one thing, reports the results of the verification, then if applicable, cleans up (usually data) and reports the overall test case result; pass or fail. 

Download custom IReportResolver example (C#) The Telerik Reporting Service is a WCF service that enables the remote access to the Telerik Reporting Engine (aka ReportProcessor). The Reporting Service acts as a communication interface between the client programs and the ReportProcessor. The client programs invoke the report rendering from the service using a string report description. Based on the report description the service’s report resolvers try to create an IReportDocument instance needed by the ReportProcessor. The IReportDocument interface represents a report document. This includes a single Report or ReportBook. The IReportDocument returned by the report resolver will be further handled by the ReportProcessor. The service...

Everyone in the mobile apps business needs real-time feedback about their app’s crashes. These have to be quickly fixed, so that you are not losing converted leads. Instead, these users need to be treated with the utmost attention. To get the feedback you have three ways to go: 1)    Use the error reporting procedure on App Hub, but you’ll have to wait for 3 to 4 days for the crash reports to be ready, which may result in losing some of  your users. 2)    Put some time and efforts and write the functionality yourself. 3)    Use Telerik ready-to-use Error Diagnostics control that allows...