Note: Cross posted from The Typemock Insider Blog. Permalink If the webinar’s not enough for you, Richard Fennell gave a presentation on the subject last week, and it’s a good one. Go take a look.
Sometimes it does. But with a supporting environment, like stated in the post, commited people around, lots of code and test review and quick feedback reporting loop it needs much less time. The problem is finding these environments. If you’re lucky enough to stumble on such a workplace stay there. After that, you can create
Note: Cross posted from The Typemock Insider Blog. Permalink Well last week’s webinar is now on our site. You can watch the SharePoint Webinar as well as download the code examples. Thank for everyone who joined, and I hope more will do so in the next ones. I had a lot of fun doing this,
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