April 2007 - Posts
Jesse has the scoop. Very big announcement from Adobe on the open sourcing of Flex.
JD has a collection of links to folks thoughts on this. The possibility of creating a .NET version of Flex is closer with the source to hand.
Going to start listing the tips that the MbUnit community post about into numbered posts. Julian kicks us off with two great posts,
Ben Hall, a long standing member of the MbUnit team will in the summer be joining
Red Gate Software as a test engineer. My heart felt congrats to Ben on landing this role, who I am certain will bring real value to the Red Gate team.
At the start of last year JetBrians talked about a creating a C# IDE but it all went quiet. Either the project was binned or its going on in secret, any clues?
Update: Some views and comments over at Ayendes place. I do wonder what the out come would be if JetBrains open sourced the IDE (highly unlikely but a fun thought).
Two great posts from the MbUnit community.
CodeBetter's Scott Bellware has two posts on the information barrier in OSS (my subtext), one on documentaion barriers in OSS and another on reading and understanding code with a slant on OSS. I left a comment on the first post but I think the second post needs a some further consideration.
Each OSS project has its own objectives, timeframes and constriants. It's important to consider that with out a corp sponsor the developers behind a OSS project are at the mercy of their dayjobs and private lives (which effects all OSS developers). The folks behind OSS projects work (mostly) for free and work very hard to help develop software to help you solve your own coding issues and deliver your own projects, the info barrier can be frustrating but OSS projects often have friendly and vibrant communities that are willing to help.
This brings me to a point in Scotts post.
"..."community" in open source jargon usually refers the the community of people involved in the development of the project rather than the community at large"
It's an interesting view from Scott, projects that are popular and been around for a good peroid of time have gained a large following and spawned articles, books and other info. Smaller projects sometimes have yet to grow this kind of information and that can be a frustration however most if not all OSS projects have mailing lists and forums with folks who can help answer your questions.
From MbUnit's point of view we have a wiki, articles and blog posts but the problem is that information is spread around. In the next few weeks I'll be addressing this more and will try and get the wiki as up to date as possible with the 2.4 release. Going further MbUnit Gallio will have a far greater degree of information both in deep technical form and more practial end user guides.
Ben has followed up his post on row tests with a post on
data driving your unit tests using MbUnits Data Fixture. If your used to working with VSTS then this feature may ring a bell in that you can allocate a data source (in MbUnits case a XML file) as a data driver over your tests.
Master Chief Peli has two samples showing Pex in action, one is a short intro to parameterized testing and the other shows a refactor of the NUnit bank sample to Pex. More to come so stayed tuned...
Vadim, who helped develop the new private member testing in the forthcoming MbUnit 2.4 release has a
great write up post on the functionality. If its a feature you liked in VSTS then this new area of functionality is worth checking out. As Vadim points out if there is anything here that can be improved then please let
the MbUnit community know.
Ben Hall has a short and sweet post on MbUnit's row test, it includes some sample code for you to try out.
The RowTest fixture in MbUnit is by far one of the most popular features and its likely to find its way into other test frameworks over time. Its one of the most simple ways of getting a range of data between x and y into your asserts. RowTest lets you test possible ranges of data (including fringe ranges that you might not consider valid) across your tests and in manner that won't have you writing 100 asserts to do so (which may very well folks off this kind of testing). The other feature in MbUnits toolbox that is related to RowTest is the Combintional (or pair wise) Fixture, you can find an example of this (and RowTest) in James Averys talk code. I'll have more to say about it at a later date.
More Posts
Next page »