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,
Note: Cross posted from The Typemock Insider Blog. Permalink And here it is. Go check it out now. Thanks Dr. Random (Casey Kramer)!
Note: Cross posted from The Typemock Insider Blog. Permalink I’m the first one who gets to break new stuff, and so, here are my impressions from Racer: It’s the greatest invention ever! What’s that? You say I’m a bit biased because I work at Typemock? You might have a point. So how’s my experience so
A long catalog of anti patterns. While interesting and lots of “I’ve done this!” moments, remember: When doing unit tests, you will make mistakes. Ok, when you program, you’ll make mistakes. You can’t say now: I got to watch out for these, you won’t write unit tests at all. Don’t let lists of patterns or