• .NET Mobile Web Kendo UI

    Why Should Developers Help With User Interface Tests?

    Automated user interface (UI) testing has a deserved reputation for being a morass of low-value, high-cost pain. Developers are already over-burdened trying to get the work in front of them completed and into the delivery pipeline. Why should they look to take on additional work in helping create functional tests at the User Interface level?
    August 04, 2014
  • .NET Testing & ALM

    2014 Buyer's Guide: Select the Best Testing Tool for Your Project

    Choosing the right test automation tool for your project can be a gruesome process. You’ll want to measure each solution against your current and future needs and you’ll need to carefully weigh these factors against open and hidden costs. Knowing where to start, and what your milestones should be, can help you save budget, time and frustration in the long run.
  • .NET Mobile

    Why Should Developers Help With User Interface Tests?

    Automated user interface (UI) testing has a deserved reputation for being a morass of low-value, high-cost pain. Developers are already over-burdened trying to get the work in front of them completed and into the delivery pipeline. Why should they look to take on additional work in helping create functional tests at the User Interface level?
    June 20, 2014
  • .NET Testing & ALM

    Telerik Test Studio R2 2014 Arrives

    I am pleased to inform our valued customers that you can now download our official R2 2014 release. This release is all about our customers – with over 140 items being addressed. We also have important news for our Windows XP users, so please read through this post in its entirety!
    June 18, 2014
  • .NET Testing & ALM

    Why Should Developers Help With User Interface Tests?

    Automated user interface (UI) testing has a deserved reputation for being a morass of low-value, high-cost pain. Developers are already over-burdened trying to get the work in front of them completed and into the delivery pipeline. Why should they look to take on additional work in helping create functional tests at the User Interface level?