Test Runner - Configuration

Configuration determines the flow/functionality of the test runner so it is key that the configuration is solid.

• Config files follow this basic structure:

<?xml version="1.0" encoding="ISO-8859-1"?>
<config>
    <scanners>
        <scanner>
            <filters></filters>
        </scanner>
    </scanners>
    <runner>
        <reporters>
            <reporter></reporter>
        </reporters>
    </runner>
</config>

• The config.xml file in /path/to/testrunner/front/config/ is used by the running processes

• All XML tags are all lowercase
• Config entries for loading class types are specified as plural (<filters></filters> specifies one or more Blerby_Filter_*) The following snippit show an extension filter to automatically be loaded

<filters>
    <filter>
        <type>Extension</type>
        <options>
            <extensions>.php,.php5,.inc</extensions>
        </options>
    </filter>
</filters>


Note: Currently there is no <runners> tag, as there is only support for 1 runner in the configuration at once (use <runner> explicitly).

Include Paths

The include paths directive makes your life easier by allowing you to specify what paths need to be added to your php include_paths configuration.

You would set these up like so:

<config>
    <includePaths>
        <path>/path/to/shared/libs/</path>
        <path>C:\path\to\shared\libs</path>
        <path>C:/another/path/to/shared/libs</path>
    </includePaths>
    ...
</config>

Summary

This is a basic 'guidelines' page for showing how a config.xml should be structured.  Some classes utilize other sets of tags such as the <options> tag seen above for passing extra params.

Please read the appropriate documentation when configuring.