I have no experience with QTP. But I know a bit to answer why QTP is or is anti-agile: 1) No support for programming languages like Java, .Net so that it allows it to be used as an acceptance testing tool. Having an acceptance test tool is very important for the team. QTP automates testing,
Note: Cross posted from The Typemock Insider Blog. Permalink We’re starting a bi-weekly webinar. The first is on Wednesday, July 15th, and is going to be about unit testing SharePoint. We’re doing a repeat on the same day, so it’s going to be one for each hemisphere. I encourage you to get one or two
Note: Cross posted from The Typemock Insider Blog. Permalink And another Typemock Racer review emerges. Thanks, Bill Craun! I really appreciate the time you put into the review. Just to remind everyone, you can download Racer and find out what it can do for you.
Note: Cross posted from The Typemock Insider Blog. Permalink Mel Grubb talks about parameterized tests and why use it at all. He also raises the question whether having the ability to run parameterized tests can rule out usage of a framework. Personally, I think there are better ways to choose unit tests framework, but that’s
Note: Cross posted from The Typemock Insider Blog. Permalink Arjan Einbu spills the beans on his experience with unit testing, busting one myth after the other. Like the “I don’t have time” excuse, if you’ve used any of these excuses, better find a new one. Scratch that, write a test. And about the one where
It’s a nice post, that covers the essentials, in addition to what I posted before. A nice plus would be the ability to run integration tests as well. The build server should be able to at least run nightly, and in such cases, why stick to just unit tests? The ideal is to build with
Note: Cross posted from The Typemock Insider Blog. Permalink A while ago, Eric Shupps wrote about TDD and SharePoint development. His follow up post is really a good read, because rather concentrating on the technique (TDD or Test After), he’s concentrating on why we do unit tests in the first place: Making better code, for
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