A.4. Debugging

Debugging and diagnostics. Useful for checking setup, for example.

A.4.1. DebugServices

Lists service class names, as picked up from configuration. Useful with AliasServices (see Section A.2.3, “AliasServices”).

A.4.2. DebugClock

Reads the current value of the clock. Useful for debugging and diagnostics.

A.4.3. DebugObjectStore

Dumps the contents of the object store. Useful for debugging setup (through SetupObjects, Section A.2.4, “SetUpObjects”, and UsingNakedObjectsViewerForSetup, Section A.3.1, “UsingNakedObjectsViewer / UsingNakedObjectsViewerForSetup”).

A.4.4. CheckSpecificationsLoaded

Verifies that listed NakedObjectSpecifications have been loaded into the metamodel.

A.4.5. RunViewer

Runs up the DnD viewer with the current state of the objects. This is a great way to inspect the state of the system, for example if a test is failing and you can't see why.

Of course, other alternatives are writing unit tests and debugging with break points. But failing scenario tests usually arise because of an integration issue between two different bits of the system. Being able to have a "poke around" can be invaluable.