Skip to content

Comments

CCXDEV-15561: Improve test coverage 4#1226

Open
katushiik11 wants to merge 5 commits intoopenshift:masterfrom
katushiik11:CCXDEV-15561-test-coverage-4
Open

CCXDEV-15561: Improve test coverage 4#1226
katushiik11 wants to merge 5 commits intoopenshift:masterfrom
katushiik11:CCXDEV-15561-test-coverage-4

Conversation

@katushiik11
Copy link
Contributor

This PR implements tests to improve test coverage in directories, utils, utils/check, controller/periodic & cmd/obfuscate-archive.

Categories

  • Bugfix
  • Data Enhancement
  • Feature
  • Backporting
  • Others (CI, Infrastructure, Documentation)

Sample Archive

  • None

Documentation

  • None

Unit Tests

  • pkg/utils/count_lines_test.go
  • pkg/utils/gatherers_test.go
  • pkg/utils/line_limit_reader_test.go
  • pkg/utils/check/has_container_in_crashloop_test.go
  • pkg/utils/check/is_healthy_pod_test.go
  • pkg/controller/periodic/datagather_informer_test.go
  • cmd/obfuscate-archive/main_test.go

Privacy

Yes. There are no sensitive data in the newly collected information.

Changelog

No

Breaking Changes

No

References

https://issues.redhat.com/browse/CCXDEV-15561

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 9, 2026
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Feb 9, 2026

@katushiik11: This pull request references CCXDEV-15561 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

This PR implements tests to improve test coverage in directories, utils, utils/check, controller/periodic & cmd/obfuscate-archive.

Categories

  • Bugfix
  • Data Enhancement
  • Feature
  • Backporting
  • Others (CI, Infrastructure, Documentation)

Sample Archive

  • None

Documentation

  • None

Unit Tests

  • pkg/utils/count_lines_test.go
  • pkg/utils/gatherers_test.go
  • pkg/utils/line_limit_reader_test.go
  • pkg/utils/check/has_container_in_crashloop_test.go
  • pkg/utils/check/is_healthy_pod_test.go
  • pkg/controller/periodic/datagather_informer_test.go
  • cmd/obfuscate-archive/main_test.go

Privacy

Yes. There are no sensitive data in the newly collected information.

Changelog

No

Breaking Changes

No

References

https://issues.redhat.com/browse/CCXDEV-15561

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested review from ncaak and opokornyy February 9, 2026 12:41
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 9, 2026
@katushiik11
Copy link
Contributor Author

/retest

2 similar comments
@BaiyangZhou
Copy link

/retest

@opokornyy
Copy link
Contributor

/retest

expected: false,
},
{
name: "should process - exactly at period boundary",
Copy link
Contributor

Choose a reason for hiding this comment

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

The third and fourth test cases looks like duplicates, imo we could drop them

@openshift-ci
Copy link

openshift-ci bot commented Feb 12, 2026

@katushiik11: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/lint 722e8fc link true /test lint

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Copy link
Contributor

@ncaak ncaak left a comment

Choose a reason for hiding this comment

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

Overall, it looks good.

I have a few minor concerns about some field names, such as "now" and "expected," which could be more specific. However, the tests are readable, so I won't push for a refactor.

I approve these changes, but I'll let @opokornyy give final approval and the "lgtm" label.

@openshift-ci
Copy link

openshift-ci bot commented Feb 19, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: katushiik11, ncaak

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants