Skip to content
This repository


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

This project facilitates acceptance testing of puppet.

Fetching latest commit…


Cannot retrieve the latest commit at this time

Octocat-spinner-32 cfg_examples
Octocat-spinner-32 ci
Octocat-spinner-32 dist
Octocat-spinner-32 lib
Octocat-spinner-32 log
Octocat-spinner-32 setup
Octocat-spinner-32 spec
Octocat-spinner-32 tarballs
Octocat-spinner-32 template
Octocat-spinner-32 tmp
Octocat-spinner-32 vmutil
Octocat-spinner-32 .gitignore
Octocat-spinner-32 README
Octocat-spinner-32 libv_host
Octocat-spinner-32 systest.rb
Running the Distributed Test Harness

Pre-flight checks:

  - You will need at least one System Undet Test (SUT) host, physical or virtual is fine.  The machine will need a properly configured network.
  - On the your SUT, you must configure pass through ssh auth for the root user.
  - The SUT have have the "ntpdate" binary installed
  - GIT installs: installing from a git repository then you must have git, ruby, rdoc installed on your SUT. 
  - PE installs: PE will install git, ruby, rdoc.

  - The harness need not be ran as root.
  - The machine that will drive the tests must have ruby installed, inclduing the following ruby gems:

Prepare a config file:

The test harness is configuration driven; the config file is yaml formated.  A basic config file sufficent for running tests against a single host:

      - master
      - agent
    platform: centos-5-i386
  rubyver: ruby18

Here we have the machine "hostname_of_test_machine", a Centos 5.x 32 bit box,, that will serve as a Pupppet master and Agent.

This represents a very basic config; more complex configs can be found under cfg_examples/.

Steps to run the acceptance tests:

./systest.rb -c your_cfg --type git -p  -f 1.5.8 -t tests/acceptance --debug

Results will be written to log/latest/summary.txt and runlog

Special topic branch checkout:
./systest.rb -c 2centos_64_386 --type git -p -f 1.5.8 -t tests/acceptance/ticket_6856_manage_not_work_with_symlinks.rb
Something went wrong with that request. Please try again.