Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change Coverage Reporting Tool #4061

Merged
merged 6 commits into from
Oct 16, 2024
Merged

Change Coverage Reporting Tool #4061

merged 6 commits into from
Oct 16, 2024

Conversation

asteel-gsa
Copy link
Contributor

@asteel-gsa asteel-gsa commented Jul 8, 2024

The other major coverage tools output too much to the PR, and make it difficult to use for Review.
cobertura-report has an outstanding issue with displaying modified files, as well as broke when the merge occurs due to this. It did not break when it output the entire coverage report to the PR
code-coverage-report-action while nice to have a diff on old coverage reports, outputs everything as if it were on the docker container and has no ability to hide 100% items.

The new action, while it doesnt display line numbers, gives the reviewer easy access to bring the testing up to 90% threshold, while keeping the pr clean.

Copy link
Contributor

github-actions bot commented Jul 8, 2024

Terraform plan for meta

No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

Warning: Argument is deprecated

  with module.s3-backups.cloudfoundry_service_instance.bucket,
  on /tmp/terraform-data-dir/modules/s3-backups/s3/main.tf line 14, in resource "cloudfoundry_service_instance" "bucket":
  14:   recursive_delete = var.recursive_delete

Since CF API v3, recursive delete is always done on the cloudcontroller side.
This will be removed in future releases

✅ Plan applied in Deploy to Development and Management Environment #838

Copy link
Contributor

github-actions bot commented Jul 8, 2024

Terraform plan for dev

Plan: 1 to add, 2 to change, 1 to destroy.
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
!~  update in-place
-/+ destroy and then create replacement

Terraform will perform the following actions:

  # module.dev.module.clamav.cloudfoundry_app.clamav_api will be updated in-place
!~  resource "cloudfoundry_app" "clamav_api" {
!~      docker_image                    = "ghcr.io/gsa-tts/fac/clamav@sha256:8119bc9c23555b7331108f0cf918cabb3303c7b44eb382aadc7a352222eb532c" -> "ghcr.io/gsa-tts/fac/clamav@sha256:9f2daecce2d94248952899f82133dee8018cc0a03a7f5330b8013b69468344a4"
        id                              = "779bbc51-f78a-4186-90eb-5acb68d7d746"
        name                            = "fac-av-dev"
#        (17 unchanged attributes hidden)

#        (1 unchanged block hidden)
    }

  # module.dev.module.cors.null_resource.cors_header must be replaced
-/+ resource "null_resource" "cors_header" {
!~      id       = "*******************" -> (known after apply)
!~      triggers = { # forces replacement
!~          "always_run" = "2024-08-17T00:33:18Z" -> (known after apply)
        }
    }

  # module.dev.module.file_scanner_clamav.cloudfoundry_app.clamav_api will be updated in-place
!~  resource "cloudfoundry_app" "clamav_api" {
!~      docker_image                    = "ghcr.io/gsa-tts/fac/clamav@sha256:8119bc9c23555b7331108f0cf918cabb3303c7b44eb382aadc7a352222eb532c" -> "ghcr.io/gsa-tts/fac/clamav@sha256:9f2daecce2d94248952899f82133dee8018cc0a03a7f5330b8013b69468344a4"
        id                              = "65c83416-4126-4785-99c2-5e1adb810422"
        name                            = "fac-av-dev-fs"
#        (17 unchanged attributes hidden)

#        (1 unchanged block hidden)
    }

Plan: 1 to add, 2 to change, 1 to destroy.

Warning: Argument is deprecated

  with module.dev-backups-bucket.cloudfoundry_service_instance.bucket,
  on /tmp/terraform-data-dir/modules/dev-backups-bucket/s3/main.tf line 14, in resource "cloudfoundry_service_instance" "bucket":
  14:   recursive_delete = var.recursive_delete

Since CF API v3, recursive delete is always done on the cloudcontroller side.
This will be removed in future releases

(and 6 more similar warnings elsewhere)

❌ Plan not applied in Deploy to Development and Management Environment #838 (Plan has changed)

@asteel-gsa asteel-gsa changed the title Sets thresholds for new Coverate Reporting Tool Sets thresholds for new Coverage Reporting Tool Jul 8, 2024
@asteel-gsa asteel-gsa requested a review from danswick July 8, 2024 21:32
@asteel-gsa
Copy link
Contributor Author

@danswick What do you think of these thresholds for the new coverage report?

@asteel-gsa asteel-gsa force-pushed the enhance-new-coverage-reporter branch from 041640e to 66b0be4 Compare July 11, 2024 15:51
@asteel-gsa asteel-gsa force-pushed the enhance-new-coverage-reporter branch from 66b0be4 to 1e53a09 Compare July 12, 2024 12:39
@asteel-gsa asteel-gsa force-pushed the enhance-new-coverage-reporter branch from 1e53a09 to 3680818 Compare July 12, 2024 13:14
@asteel-gsa asteel-gsa force-pushed the enhance-new-coverage-reporter branch from 3680818 to 8a5ef67 Compare July 19, 2024 14:18
@asteel-gsa asteel-gsa force-pushed the enhance-new-coverage-reporter branch from 1809abd to a0a43de Compare July 31, 2024 13:16
@asteel-gsa asteel-gsa force-pushed the enhance-new-coverage-reporter branch from a0a43de to 8feb360 Compare August 1, 2024 14:07
@asteel-gsa
Copy link
Contributor Author

Still unsure if the team is feeling the coverage necessity at this time. Thread on options here

@asteel-gsa asteel-gsa force-pushed the enhance-new-coverage-reporter branch from 8feb360 to 684a0de Compare August 13, 2024 16:25
@asteel-gsa asteel-gsa requested a review from a team August 13, 2024 16:25
@asteel-gsa asteel-gsa changed the title Sets thresholds for new Coverage Reporting Tool Change Coverage Reporting Tool Aug 13, 2024
@asteel-gsa asteel-gsa force-pushed the enhance-new-coverage-reporter branch from 684a0de to bcc36ea Compare August 13, 2024 18:02
@GSA-TTS GSA-TTS deleted a comment from github-actions bot Aug 14, 2024
@GSA-TTS GSA-TTS deleted a comment from github-actions bot Aug 14, 2024
@asteel-gsa asteel-gsa force-pushed the enhance-new-coverage-reporter branch from bcc36ea to ab23845 Compare August 15, 2024 17:15
Copy link
Contributor

Code Coverage

Package Line Rate Branch Rate Health
. 100% 100%
api 98% 92%
audit 97% 92%
audit.cross_validation 98% 89%
audit.fixtures 84% 43%
audit.intakelib 94% 84%
audit.intakelib.checks 95% 89%
audit.intakelib.common 98% 83%
audit.intakelib.transforms 99% 97%
audit.management.commands 78% 17%
audit.migrations 100% 100%
audit.models 95% 83%
audit.templatetags 100% 100%
audit.views 60% 45%
census_historical_migration 96% 93%
census_historical_migration.migrations 100% 100%
census_historical_migration.sac_general_lib 92% 85%
census_historical_migration.transforms 95% 90%
census_historical_migration.workbooklib 68% 66%
config 81% 12%
dissemination 93% 84%
dissemination.migrations 97% 25%
dissemination.searchlib 74% 59%
dissemination.templatetags 100% 100%
djangooidc 53% 38%
djangooidc.tests 100% 97%
report_submission 93% 90%
report_submission.migrations 100% 100%
report_submission.templatetags 74% 100%
support 95% 83%
support.management.commands 96% 100%
support.migrations 100% 100%
support.models 97% 83%
tools 98% 83%
users 98% 100%
users.fixtures 100% 83%
users.management 100% 100%
users.management.commands 100% 100%
users.migrations 100% 100%
Summary 91% (16568 / 18150) 83% (3183 / 3838)

Copy link
Contributor

@jadudm jadudm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. And, if we want to change it/go back, we can.

@jadudm jadudm added this pull request to the merge queue Oct 16, 2024
Merged via the queue into main with commit 5674d3e Oct 16, 2024
16 checks passed
@jadudm jadudm deleted the enhance-new-coverage-reporter branch October 16, 2024 15:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants