In order to succesfully run test binary, valid config.xml file needs
to be placed in binary directory.
Config file consists of multiple main sections (xml tags):
localConfiguration: used for tests run on local machineremoteConfiguration: used for tests that need additional remote machines (mainly for tests using pools with remote replicas). There can be more than oneremoteConfigurationnode.rasConfiguration: used for RAS tests by test controller machine
testDir: path to test execution directory. IfdimmConfigurationsection- is defined, it should represent a mountpoint of non-NVDIMM device.
dimmConfiguration: NVDIMM devices configuration sectionmountPoint: path to mountpoint associated with single bus connected with one or more NVDIMMS
testDir: path to test execution directory on remote host. IfdimmConfigurationsection is defined, it should represent a mountpoint of non-NVDIMM device.address: remote host address in format[<user>@]<hostname>[:<port>]with optional user and port number. Provided address needs to be sufficient to authenticate without further quering.binsDir: path to directory with pmdk-tests binaries on remote hostdimmConfiguration: same as in local configuration
DUT- node representing single testing machine managed by controlleraddress: DUT addresspowerCycleCommand: command triggering DUT power cyclebinDir: DUT test binaries directory
See also: config.xml example file.