If you are looking to get involved with test profile development, the simplest way is by starting at looking at a basic test like c-ray, tesseract or others. There are also other potential files like pre.sh, interim.sh, and post.sh for execution at pre-run, interim-run, and post-run stages by the Phoronix Test Suite. The phoronix-test-profile openbenchmarking-changes sub-command also provides users from the CLI a convenient look at recently updated tests.Ī test profile itself consists of a main XML file containing the test's meta-data ( test-definition.xml), an XML file if needed to specify required files and its MD5/SHA256 hashes and file sizes ( downloads.xml), and the install.sh script for installing the test and generating the run-script for execution by the Phoronix Test Suite at run-time. The Phoronix Test Suite checks for new test profiles/suites on a daily basis when run, though the meta-data cache can be updated manually if desired via phoronix-test-suite openbenchmarking-refresh. This allows for test profiles to be updated independent of the Phoronix Test Suite client, new tests to be added past a Phoronix Test Suite release, and other benefits. Since Phoronix Test Suite 3.0, test profiles have been versioned separately from the Phoronix Test Suite and served by when needed by the client, rather than being bundled with the phoronix-test-suite package itself.

These test profiles are not usable without the Phoronix Test Suite or from its Git repository. (This Git copy is auto-generated via phoronix-test-suite dump-tests-to-git.) This Git repository is here primarily for convenience. test profiles themselves are not stored in any Git repository but rather has relied upon its own custom version management system integrated into the Phoronix Test Suite. This Git repository serves as an auto-converted repository of all test profiles used by the Phoronix Test Suite available in the form of a Git repository.

Phoronix ram test