June 2005 - Posts
MbUnit has been making some good strides lately. We are still deep in reorganization and as a result things like download info, documentation and other info is being made available ASAP. Some frustrations have been aired about the resulting confusion and I do ask if you using MbUnit or are coming to MbUnit that you join the mailing lists. Updates and news are posted there first and until the dust settles its the very best place for info, to ask questions and find answers to your problems.
Peli beat me to it but CCNet as of build 0.9.2 has the XSL in the distro needed for you to work with MbUnit and CCNet. The XSL has been on the CCNet contribution XSL page for several months now but is now in the main distro. If your looking to get CCNet and MbUnit working then you should have all the things you need in one place now. The MbUnit and CCNet teams are working closely together running MbUnit on the ThoughtWorks build server and I hope that this friendship will continue to grow so we can bring more and more to the CCNet project.
Also in 0.9.2 is my patch for VSS beta 2 :)
If your interested in helping out on he MbUnit project in any way shape or form then please get in touch, all help welcome.
The Mono projects for this have been announced
. I wonder how progress on this can be tracked, I am certainly interested to hear how the students will approach there target projects, how they will quality control and document their work.
The climb to 30 is almost there :) Tommrow I turn 29.
Scott has a post on "blame culture" and communication
. I have commented in his post but my general take on this is that no such culture should exist and your team should always be considering its process improvement. A former QA lead of mine used the word like a chant, for without it the process's you put in place are only as good as you make them. When issues and problems happen then the finger of blame should only every point at your process's. Bugs got before your users, how, why, what in the process caused that, your unit tests, your functional tests? Using agile, is the team stucture and level right, are the tools and software right, are you implementing agile correctly. All of these things needs addressing, only with a bug system that supports process can you see why and where bug happend and improve your process so it never happens again. Blaming coders achieves nothing.
Considered by many to be one of the biggest pains in the rear is viewstate. A question I would like to pose is, how do you deal with view state, whats your common approach, how do you find viewstate in asp.net 2.0, any of you working to accessability standards and do your overcome viewstate issues?
I was pointed at this post by Ayende Rahein on his move to NUnit from MbUnit. It's always sad to see folks leave MbUnit behind when the future is so bright but folks have there reasons. I will try here to look over some of Ayende's reasons and whats in the pipe line.
there is a wealth of tool support for NUnit, and very little for MbUnit. Mainly, I was moved by easy CC.Net integration (yes, I know that MbUnit has that as well, but not built in and not as easily)
As far as I know MbUnit supports every single tool that NUnit also supports (if thats incorrect then let me know what we work we have to do), CCNet integration is something I personally did so I can answer that its very easy to do. The MbUnit installer includes a stock replacement for the unittests.xsl and I have added a replacement for tests.xsl that is available from the CCNet wiki. Obtain these files and replace the stock files and your done. Easy as that.
There is also this post that shows your how this is done with a custom plugin.
Beyond that, MbUnit ceased to give added value over NUnit some time ago, so in the end, I had to ask myself more Why? than Why Not?
I don't believe that is the case, NUnit has a great plugin in model that allows you to extend it but MbUnit has all that work done for you and also can be extended with more. The only thing I can suggest to anyone that shares Ayende's feelings is to join the MbUnit community, join the lists, start talking and sharing your feelings and see what we as a community can do to help.
The great thing about the .NET Framework is that there many things for many purposes, the trick is knowing what to use where, what works best for a given problem and what will scale/be fast enough for you needs. You often go through this thought process when deciding in your application if you should be using DataSets, DataTables or DataReaders. This is a great post on such a thought process
, loads of great comments one of whom (Atul Thakor) I work with and can kick a55 like the best of them. Well worth a read.
This article is an interesting one
, if Macromedia is embracing Eclipse is .NET support ever going to happen?
Having a look around for .NET Books, here is a couple I came across
Any more books you know of be it, NAnt, NUnit, CCNet, VSTS etc then let me know and I'll move this post to a story so I can keep it up to date.
The patch I created to get VSS 2005 and CCNet playing
is now available in CCNet builds as of 963. Thanks to Owen for integrating the patch into the code base and running the regression tests for me.
More Posts Next page »