• .NET Testing & ALM

    Manual Testing - the Next Step

    Greetings, fellow testers. A couple of weeks ago, I wrote about Manual Testing using Test Studio. As I pointed out, brining your existing manual tests into Test Studio is a great way to get started, and provides a better platform for reporting results over time than simple spreadsheets normally do. Your next step might be to take advantage of Test Studio's automation to ease your way through actually performing the manual tests. You probably have many tests that begin with the same set of instructions - log on, navigate to a particular page, perhaps creating some data - before ...
    June 03, 2013
  • .NET Testing & ALM

    Coming Soon

    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 ...
    May 31, 2013
  • .NET Testing & ALM

    Avoid Unnecessary Verifications

    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 ...
    May 31, 2013
  • .NET Testing & ALM

    Functional Testing with the Telerik Testing Framework

    [NOTE: This is a guest post from Telerik’s own Phil Japikse, one of Telerik’s Senior Developer Evangelists."] Background User Interface testing isn’t just for quality engineers.  It’s vital for developers to own part of this process as well.  The days of development silos are long gone (or at least should be!)  The process of throwing bits “down the line” is fraught with inefficiencies.  Developers are already adopting unit testing in record numbers, and this has led to a phenomenal increase in code quality. Why should it stop there?  Developers need to also take ownership of the user interface code just ...
    May 21, 2013
  • .NET Testing & ALM

    Data-Driven Test Automation

    Greetings, fellow testers. I recently attended a workshop on Acceptance Test Driven Development, during which the presenter spoke about distilling requirements down using examples. This is a great opportunity for testers and developers to work closely with Product Owners to determine exactly what output is expected from given inputs. There are also times when the code behind a function is particularly obtuse or for some other reason testing is best done via the application itself. Both of these are great opportunities for data-driven automation. Data-driven test automation lets us repeat a set of test steps automatically, using a set of ...
    May 20, 2013