Joe's JellyJoe Walnes rambling on and on about Software Development, Java and Extreme Programming.NMock - dynamic mock objects for .NET- February 17, 2003 Time to plug NMock. It's a dynamic mock object library for .NET based on work Nat Pryce did in the Java MockObjects project. It's one of those things that we wrote very quickly (completely test first, of course) in hardly any time at all. It was written last October and I've been using it on a number of projects (as have other people) with no problems - it just, like, works. All you need to do is supply it with a class or interface that needs to be mocked and it will dynamically create a new...http://radio.weblogs.com/0108103/2003/02/17.html#a131 Eclipse shortcut keys- February 17, 2003 As a recent convertee from IDEA to Eclipse, it's very hard to get your bearings unless you know the shortcut keys. So here's a list of the most useful keys. Print them out and stick to your monitor - you'll never have to touch your mouse again and you'll fly. http:wiki.truemesh.comjoeEclipseKeyshttp://radio.weblogs.com/0108103/2003/02/17.html#a130 XPDay 2- February 17, 2003 Some photos of the Agile Tools for .NET presentation Owen and I did at XPDay. What am I doing with my hand Oh and here's the slides from the presentation.http://radio.weblogs.com/0108103/2003/02/17.html#a129 Test coverage tools and mutation testing.- February 5, 2003 We first set off by requiring a 95% coverage before commit. This was a bit a pain in the ass but it was basically doable. This made sure all features in the system had tests, it's simple not possible to commit anything without tests when you set the bar as high as this. But this is doesn't necessarily it's test-first development, it's just tested development. jutopia I love test coverage tools. Another team at work was working on deciphering and robustifying a hairball project by slowly...http://radio.weblogs.com/0108103/2003/02/05.html#a128 JDO, or OR- February 3, 2003 JDO, or OR So somebody pointed me to JDO. It seems to be a good replacement for our DAO layer. Map your objects to a DB without too much complexity. But I'm quite hesitant: will it solve our performance problems Will it be as easy to convert our application as it looks Even worse: if we decide to go for JDO, do we need Sun's JDO spec, or is Castor's better Sun's spec doesn't seem to have a free implementation, which makes it riskier to invest in that option. I've heard a lot of good of...http://radio.weblogs.com/0108103/2003/02/03.html#a127 |