puppetlabs-puppet/test
Luke Kanies 58a81ba0e0 Fixing #1054 - transaction reports are always sent
This refactors how reports, catalogs, configurers, and transactions
are all related - the Configurer class manages the report, both
creating and sending it, so the transaction is now just responsible
for adding data to it.  I'm still a bit uncomfortable of the coupling
between transactions, the report, and configurer, but it's better than
it was.

This also fixes #2944 and #2973.

Signed-off-by: Luke Kanies <luke@madstop.com>
2010-01-18 23:21:52 +11:00
..
certmgr Removed extra whitespace from end of lines 2009-06-06 09:12:00 +10:00
data Fixing 2812 authorized_keys without comments fail 2009-11-21 13:38:22 +11:00
executables Fixing broken 0.24.x tests in test/. 2009-02-28 07:55:56 +00:00
language Fix #2818 - scope variable assigned with undef are not "undef" 2009-12-29 18:45:47 +11:00
lib Fix for #2745 fakedata tests not working 2009-10-23 15:49:31 +11:00
network Migrating Handler base tests from test/ to spec/ 2009-08-02 16:38:48 +10:00
other Fixing #1054 - transaction reports are always sent 2010-01-18 23:21:52 +11:00
puppet Fixing #2399 - removing client-side rrd graphs 2009-07-23 22:42:20 -07:00
rails Removed extra whitespace from end of lines 2009-06-06 09:12:00 +10:00
ral Adding integration tests for #2371 (backup refactor) 2009-08-03 15:02:56 -07:00
util Moving Setting classes into separate files 2009-08-24 11:36:20 +10:00
README Fix for #565: Final merge of changes from source:branches/execute-refactor into source:trunk 2007-04-03 15:51:18 +00:00
Rakefile Removed extra whitespace from end of lines 2009-06-06 09:12:00 +10:00
test Removed extra whitespace from end of lines 2009-06-06 09:12:00 +10:00

README

$Id$

To run all tests, run: 'rake test'.  To run an individual suite, run the file
directly.  e.g. cd test/util; ./utiltest.rb

You might need to run some tests as root.

If you do not have rake installed:
  gem install rake

## The following information is possibly out of date?

Tests are organized into a dual hierarchy: each subdirectory is
considered a test suite, and each file in the subdirectory is considered
a test case.  You can use any test case as an example of how to write
more of them, but basically the only requirements are that they each have
their own class names, their names each match /tc_.+\.r/, and that they have
the following header:

if __FILE__ == $0
    $:.unshift '..'
    $:.unshift '../../lib'
    $blinkbase = "../.."
end