ConfigFiles

Configuration Files

• Configuration Files
  • Test Run
  • Testbed
  • Test Batch
  • Harness

Test Run

-c (config)

This file defines variables defined by the user that are relevant to a single test batch execution. They become environment variables that can be referenced in a Test Specification and within a running test script. See the Run Config for examples.

############## User Test Run Configuration File ###############

# The example variables herein are user-supplied and apply to a single test run.
# They become ENV variables and can be referenced by sub-processes in the test
# specification.  You can put anything you want here, but here are some examples:

# Install this software version
PESTSOFTWAREVERSION: '123'

# To track users' test runs
PESTUSERNAME: myusername

# Keep test specifications short
PESTTESTROOT: /path/to/test/directory

Testbed

-t (testbed)

This file lists the Host Specification in the testbed. It allows test batches to be portable across similar testbeds.

############### User Testbed Configuration File ###############

# This describes the testbed nodes in a single testbed.  Create one 
# of these files for each testbed to be used in testing.

- host: (ip|hostname)
  hosttype: linux
  username: root
  password: password
- host: (ip|hostname)
  hosttype: windows
  username: DOMAIN/username
  password: password

Test Batch

-s (scripts)

This lists the processes and their execution parameters. See the Test Specification for details and examples.

############# User Test Execution Specifications ###################

# Modify this to describe the processes you want to run.

# Specify a specific host and don't wait for the command to finish
- testid: 543
  host: 127.0.0.1
  command: hostname
  bg: 1

# Execute the command on all linux hosts in the testbed twice
- testid: 234
  hosttype: linux
  command: date
  count: 2

Harness

cfg/pest.yaml

This specifies details about a single installation of PEST. This is the only configuration file that is not a required argument to pest.pl. It is always named pest.yaml and PEST expects it to be in its cfg directory. It is edited only once during installation. See the Pest Config page for details.

# This contains variables for the test harness itself.  These variables don't change
# after initial installation.

logdir: '/path/to/logs'