Files
..
2013-10-11 12:01:21 -07:00
2013-10-18 17:31:30 -07:00
2013-09-24 11:19:05 -07:00
2013-09-12 15:15:20 -07:00
2013-10-11 12:01:21 -07:00
2013-08-02 13:09:08 -07:00
2013-08-02 13:09:08 -07:00

This is the default location to store PFTT configuration files.

You provide them to PFTT like so:
pftt -config <file1>,<file2, etc...> <command>

PFTT searches conf and conf/internal and conf/app. If your config file is in another folder,
you must specify the path to it.

This folder has these 2 sub-folders
 * app - configurations for Applications (you may store app configs anywhere, this is just the default location)
 * internal - store your internal use only configuration files (usually network services, addresses
 and credentials you don't want to share. the internal folder is ignored by git)
 * internal_example - not read by PFTT, but show examples of what to put in your own 'internal' 

Examples:

Test all PHPTs on Apache
pftt -config apache phpt_all

Setup a MySQL server and put info in conf/internal/mysql.groovy.
Then, this will install & setup Drupal, IIS and MySQL (on Windows).
pftt -config drupal,iis,mysql setup

 
Config files are executable code written in Groovy.

You may define these functions:
hosts() - define remote hosts (SSH) to test against. 
		You can add 1 host for each OS/Version you support, thereby covering all OS/Versions you support in
		a single test pass.
scenarios() - provide individual Scenarios. PFTT will calculate all the permuations of these to generate ScenarioSets for you
scenario_sets() - provide whole Scenario Sets
configure_smtp() - configure an SMTPProtocol to define where to email reports to
configure_ftp() - configure an FTPClient to define a location to upload telemetry archives to