Although you could test a Naked Objects application using vanilla FitNesse, this would entail you having to write all the FitNesse fixtures to interact with the domain objects. You would also need to come up with a representation for the tables.

Tested Objects' FitNesse integration is designed to let you use FitNesse to test your Naked Objects application without all this hassle. We can use the same Naked Objects metamodel that is used for the auto-generation of its generic OOUIs to create a set of generic fixtures that interact with the domain object similarly. Using Tested Objects is therefore just a matter of using these fixtures out-of-the-box.

There are many such fixtures, but the one you will use the most often is the UsingNakedObjectsViewer fixture (see Section A.3.1, “UsingNakedObjectsViewer / UsingNakedObjectsViewerForSetup”). The screenshot below shows it in use for checking assertions at the end of a test (the "Then").

To explain this: the "tomsClaim1" is an alias to an object that has been created or obtained previously. The "perform" column lists the verb to do, in this case all checks. Other things that can be done include invoke actions, set properties and so forth. The "on member" column specifies the property, collection or action of the domain object being interacted with.

The following screenshot shows how the test is annotated after a successful run:

The end-user should be able to follow this test and could, if they want, run through the same set of steps manually themselves. Or, of course, they could just look at the test results.