Test Fixture Files

If you regularly run a number of test suites, using the same options each time, you should use a test fixture file (.mfu file). An .mfu file is like a batch file, and saves you from having to specify the test suites and their options individually each time you want to run them.

To create such a file, use the -generate-mfu test runner syntax option. Other options you also specify within the same command line will populate the .mfu file with further options; see Test Runner Syntax Options for a full list. Additionally, dynamic metadata in the source code of your tests is also used to populate the test fixture file; see Using Dynamic Metadata for more information.

Dynamic metadata can also be used to configure a 'Global' section, enabling you to set options that apply to all test cases specified to run. If you want to change any of the global options or add conditional options to the test fixture file, use an MFU-GLOBAL-COMMANDLINE-PREFIX entry-point in your sources; an example is shown in Examples of using Metadata.

It is not recommended to edit these test fixture files manually, as changes may be overwritten if the file gets regenerated. (If you use these files within the IDE's Unit Testing Framework, they are automatically recreated each time the project is built.)

Another advantage of using a test fixture file is that you can utilize the Apache Ant support to run test suites. See Example Ant Project for a simple example of how to run test fixture files and configure the output.

See Example Test Fixture File for a sample .mfu file.