FitNesse tables do not specify the code implementation, just the class and method names for the fixtures. We can reuse the whole test suite with a different set-up to verify two different implementations of the same interface. For example, we can use the same tables to check a web service layer and a local implementation by importing a different namespace.
Including individual pages
is not effective in this case, because we have to remember
to include new pages when they are created. A better approach is to use symbolic
links, which are effectively aliases for existing pages.
To include entire test suites, create a top-level page with a different
set-up, and then open properties for this page. In the Symbolic Links section, enter
the link label in the Page Name field and enter
the destination page reference[19]
in the Path To Page field.
It is best to use !contents -R to build the contents for the top-level page,
so there's no need to worry about listing individual links.
This approach is also very effective when you want to run the same test suite against several environments, for example, two databases.
