Gojko Adzic

I just pushed a small change to JUnit integration support for FitNesse to github; hopefully this should be merged with Uncle Bob’s master branch soon. The change enables you to output test run stats in Junit XML files, which can then be picked up by Hudson, TeamCity and other CI servers and integrated into their test history statistics.

To enable this feature, override the default test listener in the JUnitHelper instance you use for test runs (third constructor argument), and supply a JUnitXMLTestListener instance passing the folder where you want the XML files in the constructor argument. For example:

 String htmlOutputDir=new File(System.getProperty("java.io.tmpdir"),
                                  "fitnesse").getAbsolutePath();
  String xmlOutputDir=new File(System.getProperty("java.io.tmpdir"),
                                   "fitnesse-xml").getAbsolutePath();
  String fitNesseRootDir=".";
  JUnitXMLTestListener xmlTestListener=new JUnitXMLTestListener(xmlOutputDir);
  JUnitHelper helper =
      new JUnitHelper(fitNesseRootDir,htmlOutputDir,xmlTestListener);
    helper.assertTestPasses(".....");
 

Grab the source from my github repository. Also, check out the full example.

I will run a three day hands-on workshop on agile acceptance testing and specification by example in Berlin, Germany on April 19-21.

This three day workshop immerses the participants into a project driven by Specification by Example and Agile Acceptance Testing. Through facilitated exercises and discussion, you will learn how to bridge the communication gap between stakeholders and implementation teams, build quality into software from the start, design, develop and deliver systems fit for purpose.

This workshop is aimed at testers, business analysts and developers. It combines an introduction to Specification by Example and Agile Acceptance Testing, a set of exercises to help you get started with FitNesse – the most popular tool for agile acceptance testing – and a full day of working on realistic domain examples taken from your recent projects or a future phases of projects. This ensures that you gain real-world experience, enabling you to kick-start internal adoption of these practices in your team.

Click here for more information and to register.

As of now, the second edition of Test Driven .NET Development with FitNesse is free online. You can download the full PDF version or read the book online in HTML at http://gojko.net/fitnesse.

What’s new in this version?

Since the book was originally released, both FitNesse and the .NET FIT test runner were improved significantly. All the examples in this book are now updated to be compatible with the latest releases of FitNesse (20091121) and FitSharp (1.4). I re-wrote parts that are no longer applicable to the new FitSharp test runner, especially around Cell Operators. In a classic example of self-inflicted scope creep, I also wrote a new chapter on using domain objects directly.

I also changed the tool used for assembling the book. Instead of Apache FOP, I used XEP which will hopefully make the layout a bit better. Fonts (especially the code font) were also changed to make the book easier to read.

What about the paperback

I will make the paperback available soon. At the moment, the second edition is only available online.

Dan North gave a very inspiring talk at the Oresund Developer conference today, titled Our obsession with efficiency. His presentation focused on perceptions of efficiency and pitfalls of applying wrong efficiency models to software development. efficiency. Most efficiency is measured as budget/revenue, effort, time or activity and improvement efforts focus on these things, but according to North this is wrong. Continue Reading »

Oresund developer conference 2009 started today in Malmo, with 120 speakers planned to take the stage over three days and 8 tracks per day. This year’s theme is efficiency. Marc Lesser opened the conference with a keynote titled Accomplishing more by doing less.

Doing more by doing less sounds contradictory, but Lesser put it in context by saying “our task is to get rid of the things in our business that are not necessary and finding what is the real core of our business”. He quoted Michaelangelo: “Every block of stone has a statue inside it and it is the task of the sculptor to discover it.” Lesser suggested doing less in these five areas, and people should try to reduce them:

• Fear
• Assumptions
• Distractions
• Resistance
• Being busy

According to Lesser, doing less in these areas leads to more effectiveness, more composure and more meaning. It leads to accomplishing more of what really matters. Being busy is now a cultural status, said Lesser, often being used to avoid tasks and questions. People in the IT industry are always too busy, there is always too much to do. Lesser compared that to a carpenter who doesn’t have time to sharpen his tools, saying that “when you work with dull tools nothing much happens”. Pausing to sharpen the tools and then applying the same amount of effort leads to more effectiveness, said he, suggesting that programmers are tools themselves and that they should take time to sharpen to be more effective.

I’ll be covering Oredev on this blog over the next few days. Subscribe to my rss feed to get notified when I post a new article