Audience: testers, analysts, programmers. Learn to build refined acceptance tests in Fitnesse.

Class size: 12 to 24

Prerequisites: Fundamental knowledge of Fitnesse. This course is also an ideal follow-up to the Fitnesse Programming Crash Course.

Fitnesse combines the ease of use of a Wiki with the power of being able to define acceptance tests via a series of tables (known as Fit tables). Fitnesse tests can act as the negotiation point between programming and the business. Done well, your Fit tables can also act as the comprehensive repository of system requirements. Done poorly, your team will view Fitnesse as just another nuisance that they have to maintain.

You can learn the basics of Fitnesse in a few hours. Learning how to best express requirements in Fitnesse is another matter. Fitnesse contains numerous features that can help you turn a jumble of data into a flow that anyone in the organization, including non-technical domain experts, can readily understand. This one-day course will teach you how to take advantage of these Fitnesse features.

This is a hands-on course, where students learn to build their own working Fitnesse tests. Note that this is not a programming course and does not teach how to program fixtures. The Fitnesse Programming Crash Course provides hands-on experience in building custom Fitnesse fixtures.

Fitnesse Plus is currently offered for both C# and Java environments. We can also build support for C++ and Ruby classes if you're interested! (We also support FIT, SLIM, or both.)

Topics

Fitnesse review
Organizational considerations
  Wiki hierarchies and test suites
  Navigating the hierarchy
Fixture type review:
  Column/decision, row/query, setup, do/script, action, and other fixtures
  Row fixture arguments
  Row matching nuances
  Specifying row order
Errors and Exceptions
!contents flags
Determining the appropriate fixture type
Designing succinct and expressive fixtures
Aesthetic considerations
Graceful names
Effective use of setup, teardown, and includes
Collapsible sections
Eliminating duplication
Test naming guidelines
Test data concerns
Table flow
Annotating test pages
Markup variables
Using fixture templates
Using key fields to correlate data
Refactoring Fitnesse pages

Pricing / Details