Note: Cross posted from The Typemock Insider Blog. Permalink At the same day I posted about different usages of Isolator in the real world, that are not just regular faking, Travis Illig contacted me about an experiment he’s doing, which obviously succeeded. Travis, a Typemock MVP, used Isolator to change the behavior of a single
Note: Cross posted from The Typemock Insider Blog. Permalink This week I played with Racer and Gallio, the current incarnation of mbUnit. Did you know that Gallio comes with Typemock Isolator extensions? Anyway, Gallio has some thread manipulation classes, like TaskContainer and ThreadTask, as well as others. I tried to find deadlocks around those classes.
This post came from reading a question on our forum, as well as reading one on TDD experience. It’s about fragile tests, and the cost of maintenance. We’re talking about refactoring. And not just for making the code prettier and maintainable. We refactor and then our tests break. Well, sometimes they do, depending on how
Note: Cross posted from The Typemock Insider Blog. Permalink I like this one. I usually hear it in a much larger organizational context, but hey one developer is a micro-cosmos of the entire org, right? Alk talks about the cost saving of writing a test in terms of just running and debugging an app for
Note: Cross posted from The Typemock Insider Blog. Permalink This is a nice one by Yaron Naveh. Sure, it uses Moq and not Isolator, but what the hell. The funny thing is that currently I’m showing demos of faking DateTime.Now for testability, and suddenly wrapping it up just for testability (like in this presentation) seems
Note: Cross posted from The Typemock Insider Blog. Permalink I’ve written before how Richard Fennell is using CThru to fake a SharePoint workflow. But he’s not the only one using Isolator to solve problems. Take for example, Apostolis Bekiaros. He’s writing an MVC app, and wants to write more readable tests. Sure, he can do
The InfoQ article shows how much, and how Dave Nicolette calculated it. It’s interesting, since these “you only do it once and can’t compare it to the other way” things are a real pain. How much does TDD, unit testing, finding a bug earlier saves you? Maybe now we can tell.
Yes, hard to believe, but some people want to test in C++. Even more so, they like to do it in style, like, you know, regular devs. So here’s an add-in that does what TD.Net did to NUnit – integrated it into VS. Way to go!
What are they teaching in testing school? The Google testing blog post talks about no past leading to no future. It’s not that bleak, though. Is it because our industry is so young, and testing inside it even younger? Are we slow learners? Or slow teachers? I really like the analogy. And yes elves, so
Note: Cross posted from The Typemock Insider Blog. Permalink CThru is something like an extension method. It allows you to add functionality to an already working system, especially when you don’t access to the code inside. Richard Fennell from Black Marble is looking for a way to test SharePoint workflows. When we talked about it,