To reduce the occurrence of technical jargon in storytests, configuration information can be specified in a Suite Configuration File:
- A setting allows Fit Server, Test Runner and Folder Runner to execute tests in a single-threaded apartment.
- A list specifies fixture namespaces for Fit Server, Test Runner and Folder Runner, replacing the use of Import Fixture.
- A setting determines the code page used by Folder Runner for reading and writing files.
- A list specifies Cell Handler Lists for Fit Server, Test Runner and Folder Runner.
- FitServer socket connection to FitNesse now works on Vista.
- fit.dll is not loaded, even if it appears in an assembly list, to avoid multiple versions and invalid cast exceptions.
- Folder Runner opens files in shared read mode so other processes may have the files open.
- Import Fixture removes whitespace from namespaces.
- Row Fixture reports an error if a row is too short.
- The assemblies have been reorganized. Fit Library and Fit have been combined in fit.dll and all test classes have been moved out of fit.dll. An empty FitLibrary.dll is included for compatibility with existing project reference lists.
- To improve independence of test execution, the configuration environment is re-initialized after each individual test execution. This means that, for example, namespaces imported by Import Fixture in one test are not present in a subsequent test. To maintain compatibility with existing suite setups, this re-initialization is not done after the first test in a FitNesse suite, because Fit Server cannot detect if this is a suite setup or not.