Versions Compared

Version Old Version 8 New Version 9
Changes made by

Judith Johnson

Judith Johnson

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. The version can be passed in via command line (e.g. "6.4.0-Beta") as the whole set of tests is relevant - this would be the "Fix Version
  2. Copy ticket summary into the summary field
  3. If component is present, copy that in to the component field
  4. If EL6 == "Y" then concatenate "EL6" and Test description to description field
  5. If EL7 == "Y" then concatenate "EL7" and Test description
  6. If neither EL6 or EL7 is set, just use the test description
  7. Story points need to go into the command
  8. Create the ticket!
  9. Maybe write all the data into a new spreadsheet with the ticket number?
  10. Then copy/paste the spreadsheet into confluence



Sample csv fileor confluence table:

ComponentSummary EL6EL7DescriptionCommentStory PointsTicket numbers (added later)
pupmod-simp-simprake beaker:suites works for all suites using current PuppetfileY

Run the pupmod-simp-simp acceptance tests for the tagged version of pupmod-simp-simp included in simp-6.2.0RC1, using the appropriate tagged versions of all dependencies in its .fixtures.yml.

  • Procedures to generate .fixtures.yml with tagged versions from the simp-core Puppetfile
    1. Determine URL of Puppetfile.tracking file you wish to use. Make sure to use the raw URL, as you will be using it to download the Puppetfile.
    2. Download pupmod-simp-simp and checkout the tag listed in the Puppetfile.tracking.
    3. Run
      SIMP_RSPEC_PUPPETFILE=<Puppetfile.tracking URL> bundle exec rake spec_prep

      This will error-out for the simp module, because of entries in the .fixtures file the rake task can't figure out yet (simp-environment and simp-rsync). However, it will tell you the location of a generated fixtures file that contains entries for nearly all the dependencies, with appropriate URLS and tags from the Puppetfile.tracking.

    4. Edit the generated fixtures file to include the missing, special fixtures.
    5. Overwrite the .fixtures.yml file with the generated fixtures file
  • All tests should be run in FIPS and non-FIPS mode
    BEAKER_fips=yes bundle exec rake beaker:suites[<suite_name>]
bundle exec rake beaker:suites[<suite_name>]

1SIMP-11235
simp-corerake beaker:suites works for all suites using current PuppetfileYY

Run the following test suites with/without FIPS for CentOS6 and CentOS7 (as appropriate):

Suite Category Description Notes Result FIPS Result not FIPS
default Integration Uses components from `Puppetfile.tracking` PASSED el6_server and el7_server PASSED el6_server and el7_server
ipa Integration Uses components from `Puppetfile.tracking` with IPA clients Do not run with el6_server nodes set PASSED el7_server PASSED el7_server
install_from_rpm Release Uses RPMs from SIMP's packagecloud.io repos This test ASSUMES all modules have been released to PuppetForge and PackageCloud. TBD TBD
install_from_tar Release Uses RPMs from the tarball built in the ISO build process; Has login and rsyslog integration tests Be sure to set BEAKER_release_tarball environment variable to the URL for the RC1 tarball PASSED el7_server; FAILED el6_server: SIMP-5198 CLOSED PASSED el7_server; FAILED el6_server: SIMP-5198 CLOSED
install_from_core_module Release Uses the SIMP meta-module built locally and Puppet Forge This test ASSUMES all modules except the SIMP meta-module have been released to PuppetForge and PackageCloud. PASSED with fixes from SIMP-5370 CLOSED PASSED with fixes from SIMP-5370 CLOSED
REMINDER: To run in FIPS mode, set BEAKER_fips=yes (environment variable).

Gliffy Diagrams


2SIMP-11236, SIMP-11237

Validate that the compliance maps do not have errors on enforcement

Loop over all enforcement modes, and verify the catalog compiles. If it does not compile, there is a type error that will need to be fixed.A test was added to the default test suite in simp-core for this1SIMP-11238

...