TestContract

Test Contract

• Test Contract
  • Input
  • Output

The PEST Test Contract is modeled after Unix's crontab format in the sense that PEST doesn't really know what its running. This design-by-contract architecture means that any process that can be launched at the command line can be run by PEST. It also means that individual test processes have no dependence on the harness and existing test cases or tools can be launched by PEST. Test cases can be written in Java, Bash, DOS, Perl, or Python. PEST doesn't care.

Input

• Any command line executable, with arguments

Output

• STDOUT/STDERR are redirected to a log for each process
• Remote process return code is captured by PEST and logged as PASS for 0, and FAIL for non-zero.
  • On Unix, the harness subprocess exits with the same exit code as the remote ssh server process.
  • On Windows, the harness translates the remote exit code to fit into the Unix 8-bit exit code.