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.