• .NET Testing & ALM

    The Unexpected Truth About UI Test Automation Pilot Projects: A Survey Report

    We wanted to gain a better understanding of what it takes to be successful in the UI test automation field, so we can better guide our customers on a path to success with their automation projects. That’s why we decided to do this survey. Our goal was to explore the first steps teams in the field of automated functional testing take, as well as where they are today with their automation efforts and what helped them get there.
    November 20, 2014
  • .NET Mobile Web Kendo UI

    Functional GUI Testing and Kendo UI

    Even though Kendo UI makes it easy to build gorgeous UIs, teams regularly struggle with getting solid UI testing wrapped into their delivery flow. Teams often run into issues with asynchronous operations, difficult Document Object Model (DOM) structures, or browser incompatibilities that challenge team members writing functional UI tests.
    August 13, 2014
  • .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 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

    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?