module-postgresql/spec/support/postgres_test_config.rb

module PostgresTestConfig
  # Tests are pretty slow w/sahara, and when we destroy the VMs at the beginning
  #  of the test run.  This can be a hindrance for development but is very
  #  valuable for final testing.  This constant allows you to toggle between
  #  strict testing and less strict testing--the latter being useful for
  #  development purposes.
  HardCoreTesting = true

  # If this value is set to true, then each VM will be suspended after the tests
  # against it are completed.  This will slow things down a ton during
  # iterative development, but will save a lot of system resources by not
  # keeping all of the VMs running at the same time.
  SuspendVMsAfterSuite = true
end
A bit more refactoring of test context code 2012-12-03 01:41:35 +01:00			`module PostgresTestConfig`
Refactor tests and add CentOS6 image This commit does a fairly major refactor of how the spec tests are laid out. The main goal was to make it easier to run a subset of the tests--e.g., the ability to only run tests on a single OS via a simple rspec command. The test logic is now defined in some shared examples in the `support` directory. There are now spec folders for each distro, which contain some stubs to include the shared examples as well as a Vagrantfile for the particular distro. Also, the system-default postgres package tests now run successfully against the CentOS6 VM that is defined by the Vagrantfile. 2012-12-03 00:28:25 +01:00			`# Tests are pretty slow w/sahara, and when we destroy the VMs at the beginning`
			`# of the test run. This can be a hindrance for development but is very`
			`# valuable for final testing. This constant allows you to toggle between`
			`# strict testing and less strict testing--the latter being useful for`
			`# development purposes.`
Cleanup and move control of version into params Thanks to some tricks I learned from Nan Liu and Dan Bode, I was able to figure out a way to move all of the new version-related stuff back into the params class, and clean up some of the if/_real stuff. Basic tests for centos6 + pg 9.2 are passing. 2012-12-04 22:47:49 +01:00			`HardCoreTesting = true`
Refactor tests and add CentOS6 image This commit does a fairly major refactor of how the spec tests are laid out. The main goal was to make it easier to run a subset of the tests--e.g., the ability to only run tests on a single OS via a simple rspec command. The test logic is now defined in some shared examples in the `support` directory. There are now spec folders for each distro, which contain some stubs to include the shared examples as well as a Vagrantfile for the particular distro. Also, the system-default postgres package tests now run successfully against the CentOS6 VM that is defined by the Vagrantfile. 2012-12-03 00:28:25 +01:00
			`# If this value is set to true, then each VM will be suspended after the tests`
			`# against it are completed. This will slow things down a ton during`
			`# iterative development, but will save a lot of system resources by not`
			`# keeping all of the VMs running at the same time.`
Cleanup and move control of version into params Thanks to some tricks I learned from Nan Liu and Dan Bode, I was able to figure out a way to move all of the new version-related stuff back into the params class, and clean up some of the if/_real stuff. Basic tests for centos6 + pg 9.2 are passing. 2012-12-04 22:47:49 +01:00			`SuspendVMsAfterSuite = true`
Merge platform.pp back into params.pp Nan showed me a trick that will let us keep all of that param stuff inside of params.pp, make it a parameterized class, and still support the ability for users to specify a custom (non-system-default) pg version. This commit takes the first step towards that pattern by consolidating platform.pp and params.pp. (Everything old is new again!) 2012-12-04 05:42:20 +01:00			`end`