This test suite is for raxmlgui. It was created by mamiller around 3/15/3015. The ides of March.
There is at lease one test per option, and for multi-step workflows, typically multiple tests are provided.

Some only generate a single command line, no matter the options.
These use the raxmlhpc8_xsede interface, just to maximize the flexibility available to users.
(The raxmlhpc8_xsede interface was created to accommodate the commands required by raxmlgui).

Single command line options that use raxmlhpc8_rest_xsede are:
ancestral_states, ml_rapidbootstrap, pairwise_distances

there is one test for each of these.

Multi-line options must use the raxmlhpc2_workflow interface:
These include: 

fast_tree_search, mlsearch, ML_thorough_bootstrap, and bootstrap_consensus. 

Although all of these can generate multistep workflows, some create a single line if certain options are not invoked.

documentation.txt for each validation test has an example output file from that experiment. The output files are found in the raxmlgui directory
under /results_examples. Each documentation page for the example contains the name of the directory for the results of that experiment.
Under the directory name you will find the command line produced by this test.

The parameter settings to create a specific command line are given in  testInput.properties and test.Param.properties.
 
The basic structure of the raxmlhpc2_workflow.xml interface:

The idea was to offer all of the workflow options that raxmlGUI offers. So I called up each workflow offered in the user interfac, and selected many
options, and tried to replicate the command lines that raxmlGUI was generating. I also tried to preserve as much flexibility as possible in creating the interface.
In all cases, each workflow step for a given run has the same model as the previous one.  

The user first selects the workflow type they want. This establishes the command line for the first event in the workflow,
and confines possible subsequent steps to the subset supported by raxmlGUI. NO doubt capabilities can be expanded if usage requires it.

The user can choose parameters specific to that workflow, as well as parameters that are allowed for all workflows.
One thing that is not allowed is the changing of -f <foo> options. Here we only support what raxmlGUI supports.
However, it is my belief that all compatible otpions allowed by raxml are allowed by this interface.