October 2005 - Posts
Some good feedback on my last post. MbUnit is not longer packaged with TD.net but if you install both packages then you can use both as before with out a problem. MbUnit can be downloaded from the following page, the link on the page may change so I recommend you bookmark the page not the link. MbUnit is built on the same build server as TD.net so you can get the latest and greatest from both packages. The source for MbUnit can be downloaded from SVN, details here.
A question I have for the folks looking into MbUnit, is anything stopping you using it, if your interested in building MbUnit (and possibly contributing) what's stopping you?
Something that I have never understood is why MbUnit is so over looked. MbUnit supports the same assert set as NUnit, so much so you can flip referances and it works with out fault. MbUnit then add's more assert tests and can be extended just like NUnit. MbUnit supports the same row and data fixtures as MSTest, given MSTest supports database driven fixtures but MbUnit has XML driven fixtures and then add's a load more different fixtures. MbUhit shares the same kind of license as NUnit and like NUnit is opensource. I am still only scatching the surface, take a look at some of the past comments to see why folks are into MbUnit.
MbUnit has a wiki, mailing lists and IRC channel so if you need help getting started or want to help out then your very welcome.
Howard has a great post on Agile and Scrum.
Being honest about estimates – a developer has a much better idea how long it will take them to implement a feature than a Project Manager (even a technically savvy one). How many people have been involved in traditional project where The Project Plan has become anthropomorphized? Where The Developer tells The Project Manager that he hasn’t completed his designated task and The Project Manager looks panic stricken and says “But The Project Plan says you’d be finished today?!?!”.
Anyone got any clues where documentation/sdk might exist for the VSTS workflow API?
Unit testing gets all the fun in VSTS testing coverage, here is a link to web functional and load tests.
Why Microsoft have not provide winform functional (even Avalon functional) escapes me.
SVK is an extension of the SVN (Apache) runtime and file system to support things such as
- Disconnected Operation
- Decentralized Operation
- Merge Tracking
It's a set or Perl modules that sits on top of the SVN's current Perl bindings to provide these additional features. If you work in a disconnected fashion and may have time away from the respository then this is an ideal way of continuing to version\branch\merge your work and when you reconnect to the repository not have a nightmare time of trying to sync your work back. I do wonder why SVK is not added to SVN as an offical add-on or the work is not merged with SVN. SVK can work with other source control systems so I guess thats the reason why.
Kudos to Martin Woodward and Troy Gould on creating a VSTS source control block for CCNet, if you prefer CCNet over Team Build for your CI then this is for you. CCNet also supports a MSBuild task and has XSL reporting for MSTest (in the nightly builds) so nothing stopping you form slotting CCNet into your VSTS enviroment.
I noticed that Eclipse plug-in's for VSTS are available, would be great to see CruiseControl (the Java version) support the VSTS sourceblock.
When your working with methodologies like V-Model or RUP then your used to a grand plan design before you code. In XP your still designing but the design is far more on-going, as James Shore describes
it occurs in process not before the process. A common misunderstanding that I have seen is that XP is intended to be used as whole process, if your whiteboarding designs on the board thats not XP and cannot be used as an excuse. Nor can XP be used as excuse to develop code that has no design at all, or the design is in someones head, if you want a description for that then look no further than 'a big ball of mud'
Shelving is a new feature to VSTS, however if your like me and SVN is your source control system of choice then its nice to see how it's done in SVN. Mike Mason shows the way
This MS Research project (called MIL Unit Testing or MUTT for short :)
is an interesting project, this sort of low level testing is missing in the .NET unit test space (not a lot of folks write IL but it would be of interest to folks coding at this level, compiler developers etc).
More Posts Next page »