Uploaded image for project: 'Puppet Development Kit'
  1. Puppet Development Kit
  2. PDK-1051

rspec-puppet: Display coverage report results via the RSpec reporter

          Details

          • Type: Bug
          • Status: Closed
          • Priority: Normal
          • Resolution: Fixed
          • Affects Version/s: None
          • Fix Version/s: PDK 1.6.1
          • Component/s: None
          • Template:
          • Acceptance Criteria:
            Hide

            When running an rspec-puppet suite with `--format json`, the coverage results should be included in the JSON output.

            Show
            When running an rspec-puppet suite with `--format json`, the coverage results should be included in the JSON output.
          • Method Found:
            Needs Assessment
          • Release Notes:
            Bug Fix
          • Release Notes Summary:
            PDK will now display the results of an rspec-puppet test coverage report (if the user has enabled coverage reporting in their rspec-puppet configuration)
          • QA Risk Assessment:
            Needs Assessment

            Description

            As reported in https://github.com/puppetlabs/pdk/issues/471, it's not currently possible for PDK users to see the rspec-puppet generated resource coverage report (if they have it configured) when running `pdk test unit` as the results are currently printed directly to stdout and not sent to the RSpec reporter. This means that they are not part of the JSON object that PDK reads in to display to the user.

              Attachments

                Issue Links

                links to

                Web Link GitHub issue

                  Activity

                    People

                    • Assignee:
                      tim.sharpe Tim Sharpe
                      Reporter:
                      tim.sharpe Tim Sharpe
                    • Votes:
                      0 Vote for this issue
                      Watchers:
                      1 Start watching this issue

                      Dates

                      • Created:
                        Updated:
                        Resolved:

                        Zendesk Support