Recent changes to ConfigFiles

ConfigFiles modified by Todd Shoenfelt

Todd Shoenfelt — Tue, 26 Aug 2014 18:07:59 -0000

--- v4
+++ v5
@@ -37,9 +37,13 @@
     # This describes the testbed nodes in a single testbed.  Create one 
     # of these files for each testbed to be used in testing.

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

 Test Batch

ConfigFiles modified by aisarosenbaum

aisarosenbaum — Wed, 13 Nov 2013 00:01:40 -0000

--- v3
+++ v4
@@ -1,5 +1,7 @@
 Configuration Files
 ===
+
+[TOC]

 Test Run
 ---

ConfigFiles modified by aisarosenbaum

aisarosenbaum — Tue, 12 Nov 2013 23:38:09 -0000

--- v2
+++ v3
@@ -8,12 +8,37 @@

 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](TestSpecification) and within a running test script.  See the [Run Config](RunConfig) 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](HostSpecification) 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: 127.0.0.1 
+      hosttype: linux
+      username: root
+      password: password

 Test Batch
 ---
@@ -22,7 +47,30 @@

 This lists the processes and their execution parameters.  See the [Test Specification](TestSpecification) 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](PestConfig) page for details.
+
+    # This contains variables for the test harness itself.  These variables don't change
+    # after initial installation.
+
+    logdir: '/path/to/logs'

ConfigFiles modified by aisarosenbaum

aisarosenbaum — Tue, 12 Nov 2013 00:08:38 -0000

--- v1
+++ v2
@@ -6,23 +6,23 @@

 -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 [TestSpecification] and within a running test script.  See the [RunConfig] for examples.
+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](TestSpecification) and within a running test script.  See the [Run Config](RunConfig) for examples.

 Testbed
 ---

 -t (testbed)

-This file lists the [HostSpecification] in the testbed.  It allows test batches to be portable across similar testbeds.
+This file lists the [Host Specification](HostSpecification) in the testbed.  It allows test batches to be portable across similar testbeds.

 Test Batch
 ---

 -s (scripts)

-This lists the processes and their execution parameters.  See the [TestSpecification] for details and examples.
+This lists the processes and their execution parameters.  See the [Test Specification](TestSpecification) for details and examples.

 Harness
 ---

-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 [PestConfig] page for details.
+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](PestConfig) page for details.

ConfigFiles modified by aisarosenbaum

aisarosenbaum — Mon, 11 Nov 2013 23:57:30 -0000

Configuration Files

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 [TestSpecification] and within a running test script. See the [RunConfig] for examples.

Testbed

-t (testbed)

This file lists the [HostSpecification] in the testbed. It allows test batches to be portable across similar testbeds.

Test Batch

-s (scripts)

This lists the processes and their execution parameters. See the [TestSpecification] for details and examples.

Harness

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 [PestConfig] page for details.