Jun 22 2009

Trinidad 1.0.8 released

Published by gojko at 10:57 pm under fitnesse

Trinidad 1.0.8 is now available. Trinidad is the in-process test runner for FitNesse (java), allowing you to quickly execute, troubleshoot and debug FitNesse tests from your IDE and integrate FitNesse easily with a continuous build system through JUnit or Maven (without running the server). Version 1.0.8 changes include:

  • JUnit Suite Runner (@RunWith) that prints fitnesse test names in JUnit reports (thanks to Johannes Link)
  • Test names in suite results are now now hyperlinks to test outputs (thanks to Björn Beskow)
  • Compatibility with latest FitNesse version (20090513)

For more information, examples and download links see http://fitnesse.info/trinidad


Get notified when I post something new - subscribe via RSS or Twitter!

2 responses so far

2 Responses to “Trinidad 1.0.8 released”

  1. # Joe Cavanaghon 25 Jun 2009 at 9:03 pm

    I’m a bit confused as to the benefits of using fitnesse if you are just going to rewrap it into your IDE. Why not use Junit to begin with? It seems to be adding complexity instead of reducing it.

  2. # Marisa Sealon 08 Jul 2009 at 1:17 am

    Joe: While I have not used trinidad myself, I have a thought about your question.

    Great question, by the way. It really forced me to examine why I even use FIT and Fitnesse; why not just write integration or acceptance tests using a unit testing framework as you suggested?

    Two reasons: 1) Tables are easier for users/user representatives to understand and work with, instead of code 2) At least from my 8 years’ experience as a tester, testers are usually not also developers

    So – that makes the case (at least in my opinion) for why a team may want to use FIT and Fitnesse.

    Now, it has also been my experience that developers typically dislike working with the Fitnesse wiki; it’s essentially another language/syntax to learn, and it’s another tool to use. Also, debugging the tests is possible but requires additional configuration (starting the fitnesse server, specifying some stuff in project config, etc.)

    From the description of trinidad, it sounds like it solves some of the developers’ pain points but would still allow the team to use the more “user-friendly” so to speak Fitnese wiki.

    Like I said, good question. I really had to re-evaluate why I choose to use FIT and Fitnesse.

Trackback URI | Comments RSS

Leave a Reply