Telerik blogs

Latest

For the latest product updates, please visit Release.

  • Productivity Testing

    30 Days of TDD – Day Nine – Refactoring Basics

    As time goes on in any software development project you’ll no doubt find inefficiencies in your code that you would like to remove. Other times you’ll receive new requirements that are going to necessitate large scale changes in your existing code. And you will still occasionally find code that you’ve written in the past that will make you ask “What was I thinking when I did that?!” When these situations arrive, it’s time to look at refactoring your code.
    September 27, 2013
  • Productivity Testing

    30 Days of TDD – Day Eight – Dealing With Defects

    I’ve previously discussed a bit of the TDD workflow; start with a requirement, derive a test from the requirement, write just enough code to make that test pass, repeat. This is sometimes referred to as “Red, Green, Refactor” which I’ll be coming back to several times over the course of this series. In this post I’ll show you how this approach can be extended to dealing with software defects.
    September 25, 2013
  • Productivity Testing

    New Load and Scheduling Articles for Test Studio

    Now that Test Studio has a new scheduling and load testing architecture, our documentation updates can help you get the most out of our new and old scheduling and load testing features.  First, we have a new guide for an existing feature: our new Export Load Results walkthrough shows how to convert your Test Studio Load Test results to HTML or Excel spreadsheet format. Next, we have some help for responding to some load testing problems that may have popped up for a while: the No Results Data article explains what to do when you aren't getting results back ...
    September 24, 2013
  • Productivity Testing

    Power of Dynamic Test Lists

    Test Lists are a great way to organize tests and get execution results summarized. Telerik Test Studio includes the standard “Static” Test List that allows you to add existing tests from your project, but there is a small maintenance penalty for using the static list because each time you add a new test to your project it must be added to one of the existing test lists. One of the underlying principals of Test Studio is to decrease the overall maintenance cost traditionally associated with automated testing. Within the world of test lists we have done this by creating the ...
    September 23, 2013
  • Productivity Testing

    30 Days of TDD: Day Seven – Software Factories and DI Frameworks

    In the previous post I showed you how by starting to leverage the SOLID principles you can unlock the practice of Dependency Injection (DI). I also demonstrated how DI can help you write code that is free of static bindings, which makes your code flexible, open to change and testable. In this post I’ll demonstrate some practical techniques to manage the dependencies in your application by using software factories and DI frameworks.
    September 23, 2013