InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Fixture Gallery, a New Quick Reference For FitNesse How-To

Posted by Mike Bria on Mar 28, 2008

Sections
Process & Practices,
Architecture & Design,
Development
Topics
Agile ,
Agile Techniques ,
Delivering Quality ,
Software Testing
Tags
Acceptance Testing ,
Fit / Fitnesse ,
TDD
Gojko Adzic recently released a first version of another useful FitNesse resource for the developer community. Fixture Gallery is a new open doc cookbook by Gojko for FIT/FitNesse tests. It provides developers with a quick overview of the most important fixture types and concepts for agile acceptance testing using the FIT framework.

According the Gojko, the documentation is intended not so much as a FitNesse "first step", but rather as a quick reference for people familiar with FitNesse, and he hopes for the reference to be grown collaboratively by the community of users.

This first cut contains some useful agile acceptance testing thoughts, and information on using the fixtures from both the Fit and FitLibrary packages:
For each fixture type, this document explains the table format and fixture class structure and provides advice when to use and when not to use it. Each example is accompanied by the source code for Java and .NET FIT implementations, in a form that can be easily copied and used as a template for similar fixtures.
The new gallery information can be accessed via a print-ready PDF, an executable FitNesse wiki, or a live web site.

For more by Gojko, be sure to check out InfoQ news on using FitNesse with .NET and DBFit for testing database code.

Two other classic resources are always Ward Cunningham and Rick Mudgridge's definitive book on Fit and the FitNesse user guide wiki at the tool's home site.

No comments

Watch Thread Reply

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.