Recent changes to Home

Home modified by aisarosenbaum

aisarosenbaum — Wed, 13 Nov 2013 00:03:22 -0000

--- v15
+++ v16
@@ -1,5 +1,7 @@
 Perl System Test (PEST)
 ====
+
+[TOC]

 Description
 ----

Home modified by aisarosenbaum

aisarosenbaum — Tue, 12 Nov 2013 23:58:30 -0000

--- v14
+++ v15
@@ -7,7 +7,7 @@

 PEST makes extensive use of the [YAML](http://en.wikipedia.org/wiki/YAML) markup language for [Configuration Files](ConfigFiles), a language that can be parsed by a variety of programming languages.  The [Test Contract](TestContract), the interface between PEST and the processes it launches, is inspired by Unix's crontab and designed to be command line based, making it as simple and flexible as possible.  This allows test automation to be written *in any language*.

-While PEST was designed with [System Testing](SystemTesting) (serial and parallel process execution) in mind, it can also be used for [Functional Testing](Functional Testing) when one follows some simple [Best Practices](BestPractices).
+While PEST was designed with [System Testing](SystemTesting) (serial and parallel process execution) in mind, it can also be used for [Functional Testing](FunctionalTesting) when one follows some simple [Best Practices](BestPractices).

 **Note:** PEST is not a test framework.  It doesn't provide you modules to help you write individual test cases.  It is only a harness, with a simple, well-defined command line interface.

Home modified by aisarosenbaum

aisarosenbaum — Tue, 12 Nov 2013 19:08:09 -0000

--- v13
+++ v14
@@ -5,7 +5,7 @@
 ----
 Perl System Test (PEST) is a test harness, written in Perl, that enables running processes locally or on remote hosts via SSH.  Test processes are defined in a simple config file for execution on remote hosts, allowing a tester to run tests serially or in parallel.  The harness redirects (streams) standard out and standard error process output to an individual log for each process and logs process metadata in a separate file for each process.  This means that processes don't compete for log or console output.  See [Logging] for a complete explanation of the logs.  The harness captures the return code and execution parameters of each remote process in its metadata log.

-PEST makes extensive use of the [YAML](http://en.wikipedia.org/wiki/YAML) markup language for [Configuration Files](ConfigFiles), a language that can be parsed by a variety of programming languages.  The [Test Contract](TestContract), the interface between PEST and the processes it launches, is designed to be command line based, making it as simple and flexible as possible.  This allows test automation to be written *in any language*.
+PEST makes extensive use of the [YAML](http://en.wikipedia.org/wiki/YAML) markup language for [Configuration Files](ConfigFiles), a language that can be parsed by a variety of programming languages.  The [Test Contract](TestContract), the interface between PEST and the processes it launches, is inspired by Unix's crontab and designed to be command line based, making it as simple and flexible as possible.  This allows test automation to be written *in any language*.

 While PEST was designed with [System Testing](SystemTesting) (serial and parallel process execution) in mind, it can also be used for [Functional Testing](Functional Testing) when one follows some simple [Best Practices](BestPractices).

Home modified by aisarosenbaum

aisarosenbaum — Tue, 12 Nov 2013 19:06:53 -0000

--- v12
+++ v13
@@ -5,9 +5,9 @@
 ----
 Perl System Test (PEST) is a test harness, written in Perl, that enables running processes locally or on remote hosts via SSH.  Test processes are defined in a simple config file for execution on remote hosts, allowing a tester to run tests serially or in parallel.  The harness redirects (streams) standard out and standard error process output to an individual log for each process and logs process metadata in a separate file for each process.  This means that processes don't compete for log or console output.  See [Logging] for a complete explanation of the logs.  The harness captures the return code and execution parameters of each remote process in its metadata log.

-PEST makes extensive use of the [YAML](http://en.wikipedia.org/wiki/YAML) markup language for [Configuration Files](ConfigFiles), a language that can be parsed by a variety of programming languages.  The [Test Contract](TestContract), the interface between PEST and the processes it launches, is designed to be CLI based and as simple and flexible as possible.  This allows test automation to be written *in any language*.
+PEST makes extensive use of the [YAML](http://en.wikipedia.org/wiki/YAML) markup language for [Configuration Files](ConfigFiles), a language that can be parsed by a variety of programming languages.  The [Test Contract](TestContract), the interface between PEST and the processes it launches, is designed to be command line based, making it as simple and flexible as possible.  This allows test automation to be written *in any language*.

-While PEST was designed with [System Testing](SystemTesting) (serial and parallel process execution) in mind, it can also be used for [Functional Testing](Functional Testing) with some simple [Best Practices](BestPractices) for the latter.
+While PEST was designed with [System Testing](SystemTesting) (serial and parallel process execution) in mind, it can also be used for [Functional Testing](Functional Testing) when one follows some simple [Best Practices](BestPractices).

 **Note:** PEST is not a test framework.  It doesn't provide you modules to help you write individual test cases.  It is only a harness, with a simple, well-defined command line interface.

Home modified by aisarosenbaum

aisarosenbaum — Tue, 12 Nov 2013 17:36:22 -0000

--- v11
+++ v12
@@ -3,7 +3,7 @@

 Description
 ----
-Perl System Test (PEST) is a test harness, written in Perl, that enables running processes on nodes in a distributed testbed via SSH.  Test processes are defined in a simple config file for execution on remote hosts, allowing a tester to run tests serially or in parallel.  The harness redirects (streams) standard out and standard error process output to an individual log for each process and logs process metadata in a separate file for each process.  This means that processes don't compete for log or console output.  See [Logging] for a complete explanation of the logs.  The harness captures the return code and execution parameters of each remote process in its metadata log.
+Perl System Test (PEST) is a test harness, written in Perl, that enables running processes locally or on remote hosts via SSH.  Test processes are defined in a simple config file for execution on remote hosts, allowing a tester to run tests serially or in parallel.  The harness redirects (streams) standard out and standard error process output to an individual log for each process and logs process metadata in a separate file for each process.  This means that processes don't compete for log or console output.  See [Logging] for a complete explanation of the logs.  The harness captures the return code and execution parameters of each remote process in its metadata log.

 PEST makes extensive use of the [YAML](http://en.wikipedia.org/wiki/YAML) markup language for [Configuration Files](ConfigFiles), a language that can be parsed by a variety of programming languages.  The [Test Contract](TestContract), the interface between PEST and the processes it launches, is designed to be CLI based and as simple and flexible as possible.  This allows test automation to be written *in any language*.

Home modified by aisarosenbaum

aisarosenbaum — Tue, 12 Nov 2013 00:49:10 -0000

--- v10
+++ v11
@@ -7,7 +7,9 @@

 PEST makes extensive use of the [YAML](http://en.wikipedia.org/wiki/YAML) markup language for [Configuration Files](ConfigFiles), a language that can be parsed by a variety of programming languages.  The [Test Contract](TestContract), the interface between PEST and the processes it launches, is designed to be CLI based and as simple and flexible as possible.  This allows test automation to be written *in any language*.

-Note: PEST is not a test framework.  It doesn't provide you modules to help you write individual test cases.  It is only a harness, with a simple, well-defined interface.
+While PEST was designed with [System Testing](SystemTesting) (serial and parallel process execution) in mind, it can also be used for [Functional Testing](Functional Testing) with some simple [Best Practices](BestPractices) for the latter.
+
+**Note:** PEST is not a test framework.  It doesn't provide you modules to help you write individual test cases.  It is only a harness, with a simple, well-defined command line interface.

 Synopsis
 ----

Home modified by aisarosenbaum

aisarosenbaum — Tue, 12 Nov 2013 00:30:53 -0000

--- v9
+++ v10
@@ -15,7 +15,7 @@

 Design Requirements
 ----
-Read the [Design Requirements](DesignRequirements) to understand PEST's origins.
+Read the [Design Requirements](DesignRequirements) to understand PEST's origin.

 [[members limit=20]]
 [[download_button]]

Home modified by aisarosenbaum

aisarosenbaum — Tue, 12 Nov 2013 00:30:31 -0000

--- v8
+++ v9
@@ -5,7 +5,7 @@
 ----
 Perl System Test (PEST) is a test harness, written in Perl, that enables running processes on nodes in a distributed testbed via SSH.  Test processes are defined in a simple config file for execution on remote hosts, allowing a tester to run tests serially or in parallel.  The harness redirects (streams) standard out and standard error process output to an individual log for each process and logs process metadata in a separate file for each process.  This means that processes don't compete for log or console output.  See [Logging] for a complete explanation of the logs.  The harness captures the return code and execution parameters of each remote process in its metadata log.

-PEST makes extensive use of the YAML markup language for [Configuration Files](ConfigFiles), a language that can be parsed by a variety of programming languages.  The [Test Contract](TestContract), the interface between PEST and the processes it launches, is designed to be CLI based and as simple and flexible as possible.  This allows test automation to be written *in any language*.
+PEST makes extensive use of the [YAML](http://en.wikipedia.org/wiki/YAML) markup language for [Configuration Files](ConfigFiles), a language that can be parsed by a variety of programming languages.  The [Test Contract](TestContract), the interface between PEST and the processes it launches, is designed to be CLI based and as simple and flexible as possible.  This allows test automation to be written *in any language*.

 Note: PEST is not a test framework.  It doesn't provide you modules to help you write individual test cases.  It is only a harness, with a simple, well-defined interface.

@@ -13,5 +13,9 @@
 ----
     pest.pl -c path/to/user.yaml -t path/to/testbed.yaml -s path/to/testbatch.yaml

+Design Requirements
+----
+Read the [Design Requirements](DesignRequirements) to understand PEST's origins.
+
 [[members limit=20]]
 [[download_button]]

Home modified by aisarosenbaum

aisarosenbaum — Tue, 12 Nov 2013 00:24:43 -0000

--- v7
+++ v8
@@ -3,9 +3,11 @@

 Description
 ----
-Perl System Test (PEST) is a test harness, written in Perl, that enables running processes on nodes in a distributed testbed via SSH.  Test processes are defined in a simple config file for execution on remote hosts, allowing a tester to run tests serially or in parallel.  The harness redirects standard out and standard error process output to an individual log for each process and logs process metadata in a separate file for each process.  See [Logging] for a complete explanation of the logs.  The harness captures the return code of each remote process in the metadata log.  
+Perl System Test (PEST) is a test harness, written in Perl, that enables running processes on nodes in a distributed testbed via SSH.  Test processes are defined in a simple config file for execution on remote hosts, allowing a tester to run tests serially or in parallel.  The harness redirects (streams) standard out and standard error process output to an individual log for each process and logs process metadata in a separate file for each process.  This means that processes don't compete for log or console output.  See [Logging] for a complete explanation of the logs.  The harness captures the return code and execution parameters of each remote process in its metadata log.

-PEST makes extensive use of the YAML markup language for [Configuration Files](ConfigFiles), a language that can be parsed by a variety of programming languages.  The [Test Contract](TestContract), the interface between PEST and the processes it launches, is designed to be CLI based and as simple and flexible as possible.  This allows test automation to be written *in any language*.  
+PEST makes extensive use of the YAML markup language for [Configuration Files](ConfigFiles), a language that can be parsed by a variety of programming languages.  The [Test Contract](TestContract), the interface between PEST and the processes it launches, is designed to be CLI based and as simple and flexible as possible.  This allows test automation to be written *in any language*.
+
+Note: PEST is not a test framework.  It doesn't provide you modules to help you write individual test cases.  It is only a harness, with a simple, well-defined interface.

 Synopsis
 ----

Home modified by aisarosenbaum

aisarosenbaum — Tue, 12 Nov 2013 00:02:07 -0000

--- v6
+++ v7
@@ -5,7 +5,7 @@
 ----
 Perl System Test (PEST) is a test harness, written in Perl, that enables running processes on nodes in a distributed testbed via SSH.  Test processes are defined in a simple config file for execution on remote hosts, allowing a tester to run tests serially or in parallel.  The harness redirects standard out and standard error process output to an individual log for each process and logs process metadata in a separate file for each process.  See [Logging] for a complete explanation of the logs.  The harness captures the return code of each remote process in the metadata log.

-PEST makes extensive use of the YAML markup language for [ConfigFiles], a language that can be parsed by a variety of programming languages.  The [TestContract], the interface between PEST and the processes it launches, is designed to be CLI based and as simple and flexible as possible.  This allows test automation to be written *in any language*.  
+PEST makes extensive use of the YAML markup language for [Configuration Files](ConfigFiles), a language that can be parsed by a variety of programming languages.  The [Test Contract](TestContract), the interface between PEST and the processes it launches, is designed to be CLI based and as simple and flexible as possible.  This allows test automation to be written *in any language*.  

 Synopsis
 ----