Test spreadsheet standard and ticket creation code

Status	IN PROGRESS
Stakeholders	Liz Nemsick Jeanne Greulich Trevor Vaughan Brandon Riden (Unlicensed) plus
Outcome
Due date	28 Feb 2019
Owner	Judith Johnson

See Below Attachment for Sample spreadsheet

Background

What fields do we need?

Do we want to loop based on some of the input

How can we make the spreadsheet code-readable?

What important data did i leave out?

Fields available:

Issue number (will be created)
Ticket Summary
Ticket Type (story/sub-task)
Story Points
Label
Sprint
Component
Affects Version
Fix Version
Epic
Ticket Description

Proposed Fields in the spreadsheet

Component
Ticket summary (test desc < 100 chars)
Test description
Story Points
Comments
EL6 (Y if required)
EL7 (Y if required)

Process csv → Jira → csv → new confluence page!

Conversion Code would:

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
Copy ticket summary into the summary field
If component is present, copy that in to the component field
If EL6 == "Y" then concatenate "EL6" and Test description to description field
If EL7 == "Y" then concatenate "EL7" and Test description
If neither EL6 or EL7 is set, just use the test description
Story points need to go into the command
Create the ticket!
Maybe write all the data into a new spreadsheet with the ticket number?
Then copy/paste the spreadsheet into confluence

Start with this table and edit, then upload to testing confluence page. The code can be run and we'll update confluence.

Sample csv or confluence table:

Component

Summary

EL6

EL7

Description

Comment

Story Points

Ticket numbers (added later)

pupmod-simp-simp

rake beaker:suites works for all suites using current Puppetfile

Y

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>]

1

SIMP-11235

simp-core

rake beaker:suites works for all suites using current Puppetfile

Y

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

2

SIMP-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 this

1

SIMP-11238

Creates these tickets:

SIMP-11236

Summary: EL6 - rake beaker:suites works for all suites using current Puppetfile

Component: pupmod-simp-simp

Description:

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
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.
Download pupmod-simp-simp and checkout the tag listed in the Puppetfile.tracking.
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.

Edit the generated fixtures file to include the missing, special fixtures.
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>]

Fix Version: 6.4.0

Story Points: 1

Comment:

SIMP-11237

Summary: EL6 - rake beaker:suites works for all suites using current Puppetfile

Component: simp-core

Description:

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

Fix Version: 6.4.0

Story Points: 1

Comment:

SIMP-11238

Summary: EL7 - rake beaker:suites works for all suites using current Puppetfile

Component: simp-core

Description:

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

Fix Version: 6.4.0

Story Points: 2

Comment:

SIMP-11239

Summary: Validate that the compliance maps do not have errors on enforcement

Component:

Description: 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.

Fix Version: 6.4.0

Story Points: 1

Comment: A test was added to the default test suite in simp-core for this

Action items

ensure we have the necessary fields
decide whether to use yaml or csv
decide what repo to use (suggestion: a folder in https://github.com/simp/releng-misc wit the csvs as well as the ruby)
make it happen!