Latest

  • Testing & ALM

    30 Days of TDD – Day 17 – Specifying Order of Execution in Mocks

    October 25, 2013 Share
    We’ll continue developing our e-commerce application today by looking closer at how we will utilize the Order Fulfillment service. This service is provided by a third party and the API requires an ordered set of calls to be executed. In this post I’ll show you how your mocks can enforce this rule and let you know when your test violate it.

  • .NET Testing & ALM

    Coming Soon - a Richer HTML5 Testing Experience

    October 23, 2013 Share
    Earlier this year we released Test Studio 2013, and our product team has been working hard on the next release ever since. We'll be showing you some of our upcoming features over the next few weeks, and I'm happy to kick things off by showing a little more love for HTML5. Now, before we look at Test Studio's new HTML5 support, I've got to point out that everything depends on the browsers' support. If your team has been developing HTML5 applications, you're probably already aware of sites like The HTML5 Test and Can I Use - be sure to visit ...
  • Testing & ALM

    30 Days of TDD – Day 16 – Using Specific Parameters in Stubs

    October 23, 2013 Share
    In a previous post we created a relatively simple stub to stand in for our OrderDataService. Our current stub is setup to return a canned result without worrying too much about what the value of our input parameter is. There are cases where a mock like this acceptable, but in most cases you’ll find that you want to have a specific response for a specific parameter. Luckily that’s not very difficult and today we will create a stub with that exact ability.

  • .NET Testing & ALM

    The Truth About Agile | Top 30 Agile Myths- BUSTED

    October 23, 2013 Share
    Agile is not suitable for fixed bid projects Before looking at this myth, it’s important to define “Fixed bid projects”. Does this mean fixed scope, schedule, and cost? History has proven that software projects of any significance in size or complexity cannot be accurately estimated well. What is more, according to CHAOS reports 24% of all projects fail and 44% are significantly challenged2. Regardless of the project management methodology, attempting to fix all three does not have a high probability of success. Something has to give – whether it’s adding resources, cutting scope, or moving the delivery date. As described ...
  • Testing & ALM

    30 Days of TDD – Day 15 - “Simple” Does Not Always Mean “Obvious” Pt. 2

    October 21, 2013 Share
    In the last post we wrote what should have been a simple test. But in this case we’ll see how sometimes simple tests can be a little more complicated that we anticipate.