Latest

  • .NET Testing & ALM

    What Was I Thinking When I Named That?

    I was recently asked how automated tests should be named to reflect they were built using Test Studio. My response, hopefully not too blunt, was “Don’t.” Good naming conventions in software are critical. Code is read, re-read, re-re-read, and re-re-re-read 5,632 times more than it’s edited1. Readability is critical to maintaining and understanding our software. With that in mind, great names for classes, methods, variables, and tests are crucial! We need to ensure we’re able to quickly discern what the system’s behavior is, or what a particular test is covering. Good names are about intent, not implementation...
    September 13, 2013
  • .NET Testing & ALM

    Why the Cloud is Disrupting Testing Practices

    My first realization that cloud computing was changing the dynamics of software development and testing was at a conference about five years ago where two guys got up and described how they bootstrapped their fledgling software development business by spending about $200 buying server time with Amazon’s cloud services.  Rather than spending tens of thousands of dollars on servers and system administrators, they in effect outsourced those costs to the cloud provider. Since that time, the economics and flexibility of cloud computing have revolutionized all aspects of software, enabling companies large and small to avoid large infrastructure costs while rapidly ...
    September 11, 2013
  • .NET Testing & ALM

    The Importance of Timeboxing and Iterations for Agile Planning

    (In this blog post we share the first two of the areas that we address in our new free ebook called Ultimate Agile Planning Handbook) Timebox – Everything Timeboxing refers to the act of putting strict time boundaries around an action or activity. For example, you may want to timebox a meeting to be 30 minutes long to help ensure that the meeting will begin and end on time with no exceptions. When you timebox an event the result is a natural tendency to focus on the most important “stuff” first. If you time box a meeting, you would ...
    September 11, 2013
  • Testing & ALM

    30 Days of TDD: Day Two – A Review of Object Oriented Principles

    In today’s post I’ll be doing a quick review of principals of Object Oriented Programming (OOP). This post will help frame future posts in this series by ensuring that we are all on the same page in terms of our understanding of software development. Even if you are seasoned developer I recommend that you at least read the section on Polymorphism and Interfaces as these topics are widely misunderstood and are crucial to building good TDD practices.
    September 11, 2013
  • .NET Testing & ALM

    Lookin' for Tests in all the Wrong Places

    Greetings, fellow testers. Last week I was asked a question about testing output, specifically if I could help with an example of a test verifying that a list in an application has been properly sorted. This is actually a fairly common question, and is one that we cover in our documentation. I mention it here for two reasons. In part to point out the example code section of Test Studio's online documentation, but mostly because the documented example is correct but in my opinion it’s only half of the story – the second half. The first thing I’d recommend is ...
    September 11, 2013