The ClassPath: Telling Fit Nesse Where the Fixture Code Is
For a given Sub Wiki of test pages, you can specify to Fit Nesse where it can find all of the fixture classes it needs by supplying a so-called Class Path definition, which is a full absolute filepath to the directory that contains the package (in Java) or assembly (in C#) in which all the compiled classes can be found. Simply include a Class Path definition on the main page of your Sub Wiki.
The wiki markup widget you use is the !path widget. The format, in wiki markup language, looks like this:
And on a page, the same definition looks like this:
How Fit Locates Class Path Definitions in SubWikisWhenever Fit processes test tables on a given page, it build its own internal class path by finding the !path directives on the current page, and on every ancestor page. In other words, it looks up the page hierarchy of SubWikis.
This makes it possible for you to use !path directives on sub pages to override !path directives on parent pages. Thus you can create global classpaths, project specific classpaths, and even module-specific classpaths.
Learning MoreIf you are interested in Fit Nesse fixture code in general, check out Fixture Code. For information on organizing test pages into hierarchies, see Sub Wiki and Test Suites.
Keyboard Shortcuts ?