Skip to content

NETOBSERV-2653 & NETOBSERV-2689: TLS updates and PF pre-migration refactor changes#1395

Merged
memodi merged 3 commits intonetobserv:mainfrom
Amoghrd:netobserv-2653
Apr 8, 2026
Merged

NETOBSERV-2653 & NETOBSERV-2689: TLS updates and PF pre-migration refactor changes#1395
memodi merged 3 commits intonetobserv:mainfrom
Amoghrd:netobserv-2653

Conversation

@Amoghrd
Copy link
Copy Markdown
Member

@Amoghrd Amoghrd commented Mar 31, 2026

Description

Dependencies

#1398

Checklist

  • Does the changes in PR need specific configuration or environment set up for testing?
    • if so please describe it in PR description.
  • I have added thorough unit tests for the change.
  • QE requirements (check 1 from the list):
    • Standard QE validation, with pre-merge tests unless stated otherwise.
    • Regression tests only (e.g. refactoring with no user-facing change).
    • No QE (e.g. trivial change with high reviewer's confidence, or per agreement with the QE team).

Jenkins run: noo-frontend-tests#36
Another run: noo-frontend-tests#41

Summary by CodeRabbit

  • Tests
    • Refined Cypress tests to explicitly open and verify column selection, ensuring selected columns appear in tables.
    • Tightened assertions for time/RTT labels and DNS edge handlers to require numeric millisecond values.
    • Improved cleanup to tolerate already-removed test resources without failing.

@Amoghrd Amoghrd changed the title Remove DSCP column as default in tests WIP: Remove DSCP column as default in tests Mar 31, 2026
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Mar 31, 2026

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review
📝 Walkthrough

Walkthrough

Tightened regex assertions in two dashboard tests, made the DSCP column test explicitly interact with the columns modal (checks #Dscp, reloads, verifies column) and removed a call to netflowPage.stopAutoRefresh(), and made pod cleanup resilient by adding --ignore-not-found to oc delete.

Changes

Cohort / File(s) Summary
Regex Assertion Tightening
web/cypress/integration-tests/dns_dashboards.cy.ts, web/cypress/integration-tests/flowRTT_dashboards.cy.ts
Replaced permissive regex /\d* ms/gm with stricter /\d+\s*ms/ to require at least one digit followed by optional whitespace and ms.
DSCP Column Test Flow
web/cypress/integration-tests/table_queryopts.cy.ts
Test now opens the columns modal, asserts visibility, checks #Dscp, reloads the page, and verifies the Dscp column is present. Removed the netflowPage.stopAutoRefresh() call.
Pod Cleanup Resilience
web/cypress/integration-tests/netflow_external_subnet.cy.ts
Added --ignore-not-found to oc delete -f cypress/fixtures/test-pod.yaml in the after("all tests", ...) cleanup to avoid failing when the pod is missing.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Suggested labels

lgtm

Suggested reviewers

  • jotak
  • jpinsonneau
🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Title check ⚠️ Warning The PR title references NETOBSERV-2653 & NETOBSERV-2689 with vague descriptors 'TLS updates' and 'PF pre-migration refactor changes', but the actual changes are purely test fixes: DSCP column handling, DNS/FlowRTT regex assertions, and pod cleanup tolerance. Update title to reflect actual changes, e.g., 'Fix flaky Cypress tests: tighten DNS/FlowRTT assertions, update DSCP test flow, add cleanup tolerance'.
✅ Passed checks (2 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description check ✅ Passed PR description covers main changes, dependencies, and QE requirements clearly with regression tests selected.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@Amoghrd Amoghrd changed the title WIP: Remove DSCP column as default in tests WIP: NETOBSERV-2653: Remove DSCP column as default in tests Mar 31, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Collaborator

openshift-ci-robot commented Mar 31, 2026

@Amoghrd: This pull request references NETOBSERV-2653 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 story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Description

DSCP column is not going to be default once the TLS PR's are merged

Dependencies

n/a

Checklist

  • Does the changes in PR need specific configuration or environment set up for testing?
    • if so please describe it in PR description.
  • I have added thorough unit tests for the change.
  • QE requirements (check 1 from the list):
  • Standard QE validation, with pre-merge tests unless stated otherwise.
  • Regression tests only (e.g. refactoring with no user-facing change).
  • No QE (e.g. trivial change with high reviewer's confidence, or per agreement with the QE team).

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-robot
Copy link
Copy Markdown
Collaborator

openshift-ci-robot commented Mar 31, 2026

@Amoghrd: This pull request references NETOBSERV-2653 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 story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Description

DSCP column is not going to be default once the TLS PR's are merged

Dependencies

n/a

Checklist

  • Does the changes in PR need specific configuration or environment set up for testing?
    • if so please describe it in PR description.
  • I have added thorough unit tests for the change.
  • QE requirements (check 1 from the list):
  • Standard QE validation, with pre-merge tests unless stated otherwise.
  • Regression tests only (e.g. refactoring with no user-facing change).
  • No QE (e.g. trivial change with high reviewer's confidence, or per agreement with the QE team).

Summary by CodeRabbit

  • Tests
  • Improved integration test for column selection verification to enhance validation of the column state functionality.

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.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

🧹 Nitpick comments (1)
web/cypress/integration-tests/table_queryopts.cy.ts (1)

109-115: Re-assert refresh state after reload to avoid flaky DSCP checks.

stopAutoRefresh() is called before cy.reload(). If reload restores default refresh, the table may update while validating DSCP values. Re-apply or assert refresh-off after Line 114.

Proposed adjustment
 it("(OCP-68125, aramesha, Network_Observability) should verify DSCP column", function () {
     netflowPage.stopAutoRefresh()
     cy.openColumnsModal().then(col => {
         cy.get(colSelectors.columnsModal).should('be.visible')
         cy.get('#Dscp').check()
     })
     cy.reload()
+    netflowPage.stopAutoRefresh()

     cy.byTestID('table-composable').should('exist').within(() => {
         cy.get(colSelectors.dscp).should('exist')
     })
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@web/cypress/integration-tests/table_queryopts.cy.ts` around lines 109 - 115,
After reloading the page, ensure the auto-refresh remains disabled before
interacting with the DSCP checkbox: after cy.reload() call either re-invoke
netflowPage.stopAutoRefresh() or assert the refresh state is off (e.g., via a
visible UI indicator or a method like netflowPage.isAutoRefreshEnabled()
returning false), then reopen the columns modal (using cy.openColumnsModal())
and proceed to check '#Dscp' (refer to colSelectors.columnsModal and the
existing stopAutoRefresh() call); this prevents the table from refreshing during
the DSCP assertion and avoids flakiness.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@web/cypress/integration-tests/table_queryopts.cy.ts`:
- Around line 109-115: After reloading the page, ensure the auto-refresh remains
disabled before interacting with the DSCP checkbox: after cy.reload() call
either re-invoke netflowPage.stopAutoRefresh() or assert the refresh state is
off (e.g., via a visible UI indicator or a method like
netflowPage.isAutoRefreshEnabled() returning false), then reopen the columns
modal (using cy.openColumnsModal()) and proceed to check '#Dscp' (refer to
colSelectors.columnsModal and the existing stopAutoRefresh() call); this
prevents the table from refreshing during the DSCP assertion and avoids
flakiness.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: ff7e7648-9c93-4b60-86c7-84257f93a9d5

📥 Commits

Reviewing files that changed from the base of the PR and between 48d48a8 and 46edf23.

📒 Files selected for processing (1)
  • web/cypress/integration-tests/table_queryopts.cy.ts

jotak
jotak previously approved these changes Mar 31, 2026
Copy link
Copy Markdown
Member

@jotak jotak left a comment

Choose a reason for hiding this comment

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

thanks!

@openshift-ci openshift-ci Bot added the lgtm label Mar 31, 2026
@Amoghrd Amoghrd requested a review from memodi April 1, 2026 14:35
@Amoghrd Amoghrd changed the title WIP: NETOBSERV-2653: Remove DSCP column as default in tests NETOBSERV-2653: Remove DSCP column as default in tests Apr 1, 2026
@Amoghrd
Copy link
Copy Markdown
Member Author

Amoghrd commented Apr 1, 2026

TLS PRs merged

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Apr 1, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from jotak. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@openshift-ci-robot
Copy link
Copy Markdown
Collaborator

openshift-ci-robot commented Apr 1, 2026

@Amoghrd: This pull request references NETOBSERV-2653 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 story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Description

DSCP column is not going to be default once the TLS PR's are merged

Dependencies

n/a

Checklist

  • Does the changes in PR need specific configuration or environment set up for testing?
    • if so please describe it in PR description.
  • I have added thorough unit tests for the change.
  • QE requirements (check 1 from the list):
  • Standard QE validation, with pre-merge tests unless stated otherwise.
  • Regression tests only (e.g. refactoring with no user-facing change).
  • No QE (e.g. trivial change with high reviewer's confidence, or per agreement with the QE team).

Summary by CodeRabbit

  • Tests
  • Improved integration test for column selection: stops auto-refresh earlier, opens column modal, selects DSCP, reloads, and verifies the DSCP column displays as expected.
  • Tightened DNS dashboard latency assertion to require one or more digits followed by optional space and "ms", making the check stricter and more precise.

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-robot
Copy link
Copy Markdown
Collaborator

openshift-ci-robot commented Apr 1, 2026

@Amoghrd: This pull request references NETOBSERV-2653 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 story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Description

DSCP column is not going to be default once the TLS PR's are merged

Dependencies

n/a

Checklist

  • Does the changes in PR need specific configuration or environment set up for testing?
    • if so please describe it in PR description.
  • I have added thorough unit tests for the change.
  • QE requirements (check 1 from the list):
  • Standard QE validation, with pre-merge tests unless stated otherwise.
  • Regression tests only (e.g. refactoring with no user-facing change).
  • No QE (e.g. trivial change with high reviewer's confidence, or per agreement with the QE team).

Summary by CodeRabbit

  • Tests
  • Improved DSCP column integration test: stops auto-refresh earlier, opens column modal, selects DSCP, reloads, and verifies the column displays as expected.
  • Tightened DNS dashboard latency assertion to require one or more digits followed by optional space and "ms".
  • Made test cleanup tolerant of missing resources during pod deletion.
  • Added a brief wait when verifying dashboard panels to reduce flakiness.
  • Increased interaction reliability by ensuring controls are visible before clicking and adjusting readiness checks for deployment logic.

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.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

🧹 Nitpick comments (2)
web/cypress/views/netobserv.ts (1)

145-145: Selector change looks correct but relies on fragile :nth-child(2).

Waiting for loading-box__loaded before checking gridcell existence is the right approach—ensures the DOM is in a stable loaded state. However, :nth-child(2) is brittle; any DOM restructuring will break this.

Consider extracting this selector into a constant (like the pluginSelectors pattern used elsewhere) to make it easier to update if the DOM changes.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@web/cypress/views/netobserv.ts` at line 145, Extract the fragile selector
'div.loading-box__loaded:nth-child(2)' into a named constant (following the
pluginSelectors pattern used elsewhere) and replace the inline string in the
cy.get call with that constant; while extracting, prefer a more robust selector
(e.g., a class-only '.loading-box__loaded' combined with a stable data-test
attribute or a deterministic index like .eq(1) if necessary) so the test doesn't
rely on DOM child ordering — update the constant name (e.g.,
LOADING_BOX_LOADED_SECOND) and change the
cy.get('div.loading-box__loaded:nth-child(2)') usage to
cy.get(LOADING_BOX_LOADED_SECOND).
web/cypress/views/dashboards-page.ts (1)

59-67: Replace fixed delay with condition-based retry.

The hard-coded cy.wait(3000) on line 63 slows tests without guaranteeing the metrics data loads. Instead, rely on Cypress retries with the existing timeouts to wait until the condition is met (no empty-state class).

Proposed refactor
-        // Give dashboards additional time to load metrics data
-        cy.wait(3000)
-
-        // Check that the graph body doesn't have empty state class
-        cy.byTestID(names[i]).find(graphSelector.graphBody, { timeout: 120000 })
-            .should('not.have.class', 'pf-v6-c-empty-state')
+        // Check graph body once data is rendered (retry-driven, no fixed sleep)
+        cy.byTestID(names[i], { timeout: 120000 })
+            .find(graphSelector.graphBody, { timeout: 120000 })
+            .should('not.have.class', 'pf-v6-c-empty-state')
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@web/cypress/views/dashboards-page.ts` around lines 59 - 67, Remove the
hard-coded cy.wait(3000) and rely on Cypress' retry/timeouts to wait for metrics
to load; keep the existing existence check cy.byTestID(names[i], { timeout:
120000 }).should('exist') and then use
cy.byTestID(names[i]).find(graphSelector.graphBody, { timeout: 120000
}).should('not.have.class', 'pf-v6-c-empty-state') (or chain the find off the
initial cy.byTestID call) so the test retries until the graph body no longer has
the empty-state class instead of using a fixed delay.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@web/cypress/views/dashboards-page.ts`:
- Around line 59-67: Remove the hard-coded cy.wait(3000) and rely on Cypress'
retry/timeouts to wait for metrics to load; keep the existing existence check
cy.byTestID(names[i], { timeout: 120000 }).should('exist') and then use
cy.byTestID(names[i]).find(graphSelector.graphBody, { timeout: 120000
}).should('not.have.class', 'pf-v6-c-empty-state') (or chain the find off the
initial cy.byTestID call) so the test retries until the graph body no longer has
the empty-state class instead of using a fixed delay.

In `@web/cypress/views/netobserv.ts`:
- Line 145: Extract the fragile selector 'div.loading-box__loaded:nth-child(2)'
into a named constant (following the pluginSelectors pattern used elsewhere) and
replace the inline string in the cy.get call with that constant; while
extracting, prefer a more robust selector (e.g., a class-only
'.loading-box__loaded' combined with a stable data-test attribute or a
deterministic index like .eq(1) if necessary) so the test doesn't rely on DOM
child ordering — update the constant name (e.g., LOADING_BOX_LOADED_SECOND) and
change the cy.get('div.loading-box__loaded:nth-child(2)') usage to
cy.get(LOADING_BOX_LOADED_SECOND).

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 2f1ecb33-5648-49dc-84f3-ecb30e0a69a6

📥 Commits

Reviewing files that changed from the base of the PR and between 191dc71 and 30f2a73.

📒 Files selected for processing (6)
  • web/cypress/integration-tests/dns_dashboards.cy.ts
  • web/cypress/integration-tests/netflow_external_subnet.cy.ts
  • web/cypress/integration-tests/table_queryopts.cy.ts
  • web/cypress/views/dashboards-page.ts
  • web/cypress/views/netflow-page.ts
  • web/cypress/views/netobserv.ts
🚧 Files skipped from review as they are similar to previous changes (2)
  • web/cypress/integration-tests/dns_dashboards.cy.ts
  • web/cypress/integration-tests/table_queryopts.cy.ts

@openshift-ci-robot
Copy link
Copy Markdown
Collaborator

openshift-ci-robot commented Apr 1, 2026

@Amoghrd: This pull request references NETOBSERV-2653 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 story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Description

  • DSCP column is not going to be default once the TLS PR's are merged
  • Fixed regex for flaky DNS and FlowRTT test

Dependencies

n/a

Checklist

  • Does the changes in PR need specific configuration or environment set up for testing?
    • if so please describe it in PR description.
  • I have added thorough unit tests for the change.
  • QE requirements (check 1 from the list):
  • Standard QE validation, with pre-merge tests unless stated otherwise.
  • Regression tests only (e.g. refactoring with no user-facing change).
  • No QE (e.g. trivial change with high reviewer's confidence, or per agreement with the QE team).

Summary by CodeRabbit

  • Tests
  • Improved DSCP column integration test: stops auto-refresh earlier, opens column modal, selects DSCP, reloads, and verifies the column displays as expected.
  • Tightened DNS dashboard latency assertion to require one or more digits followed by optional space and "ms".
  • Made test cleanup tolerant of missing resources during pod deletion.
  • Added a brief wait when verifying dashboard panels to reduce flakiness.
  • Increased interaction reliability by ensuring controls are visible before clicking and adjusting readiness checks for deployment logic.

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-robot
Copy link
Copy Markdown
Collaborator

openshift-ci-robot commented Apr 1, 2026

@Amoghrd: This pull request references NETOBSERV-2653 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 story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Description

  • DSCP column is not going to be default once the TLS PR's are merged
  • Fixed regex for flaky DNS and FlowRTT test

Dependencies

n/a

Checklist

  • Does the changes in PR need specific configuration or environment set up for testing?
    • if so please describe it in PR description.
  • I have added thorough unit tests for the change.
  • QE requirements (check 1 from the list):
  • Standard QE validation, with pre-merge tests unless stated otherwise.
  • Regression tests only (e.g. refactoring with no user-facing change).
  • No QE (e.g. trivial change with high reviewer's confidence, or per agreement with the QE team).

Summary by CodeRabbit

  • Tests
  • Refined Cypress test assertions for improved accuracy across dashboard and table components.
  • Improved test assertion patterns for time-based value validation.
  • Enhanced test cleanup procedures to handle resource removal edge cases more robustly.

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.

@Amoghrd
Copy link
Copy Markdown
Member Author

Amoghrd commented Apr 2, 2026

/retest

@openshift-ci-robot
Copy link
Copy Markdown
Collaborator

openshift-ci-robot commented Apr 2, 2026

@Amoghrd: This pull request references NETOBSERV-2653 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 story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Description

  • DSCP column is not going to be default once the TLS PR's are merged
  • Fixed regex for flaky DNS and FlowRTT test

Dependencies

n/a

Checklist

  • Does the changes in PR need specific configuration or environment set up for testing?
    • if so please describe it in PR description.
  • I have added thorough unit tests for the change.
  • QE requirements (check 1 from the list):
  • Standard QE validation, with pre-merge tests unless stated otherwise.
  • Regression tests only (e.g. refactoring with no user-facing change).
  • No QE (e.g. trivial change with high reviewer's confidence, or per agreement with the QE team).

Summary by CodeRabbit

  • Tests
  • Refined Cypress tests to explicitly open and verify column selection, ensuring selected columns appear in tables.
  • Tightened assertions for time/RTT labels and DNS edge handlers to require numeric millisecond values.
  • Improved cleanup to tolerate already-removed test resources without failing.

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.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@web/cypress/integration-tests/table_queryopts.cy.ts`:
- Around line 109-113: The test opens the columns modal with openColumnsModal(),
checks the '#Dscp' checkbox, then reloads without persisting the selection so
the change can be lost; modify the test to explicitly persist the selection by
interacting with the modal's save/confirm control (the modal referenced by
colSelectors.columnsModal) after checking '#Dscp' before calling cy.reload(),
ensuring the checked state survives the reload.
- Around line 108-114: Reintroduce the "refresh-off" guard around the DSCP
column test to avoid racey assertions: call the existing auto-refresh disable
helper before invoking cy.openColumnsModal() (so table auto-updates won't mutate
state while checking colSelectors.columnsModal and toggling '#Dscp'), perform
the check and cy.reload(), then re-enable auto-refresh after the reload using
the corresponding enable helper; ensure the disable/enable calls bracket the
sequence to keep the test deterministic.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e0d3172c-5135-4db5-ac89-4f3a214c7e94

📥 Commits

Reviewing files that changed from the base of the PR and between f0fb846 and 092f409.

📒 Files selected for processing (4)
  • web/cypress/integration-tests/dns_dashboards.cy.ts
  • web/cypress/integration-tests/flowRTT_dashboards.cy.ts
  • web/cypress/integration-tests/netflow_external_subnet.cy.ts
  • web/cypress/integration-tests/table_queryopts.cy.ts
✅ Files skipped from review due to trivial changes (1)
  • web/cypress/integration-tests/netflow_external_subnet.cy.ts
🚧 Files skipped from review as they are similar to previous changes (2)
  • web/cypress/integration-tests/dns_dashboards.cy.ts
  • web/cypress/integration-tests/flowRTT_dashboards.cy.ts

Comment thread web/cypress/integration-tests/table_queryopts.cy.ts
Comment thread web/cypress/integration-tests/table_queryopts.cy.ts
@Amoghrd
Copy link
Copy Markdown
Member Author

Amoghrd commented Apr 6, 2026

/retest

Comment thread web/cypress/integration-tests/table_queryopts.cy.ts
@Amoghrd Amoghrd force-pushed the netobserv-2653 branch 3 times, most recently from 2f4faa6 to 38bdf61 Compare April 7, 2026 19:17
@Amoghrd
Copy link
Copy Markdown
Member Author

Amoghrd commented Apr 7, 2026

/hold

@Amoghrd Amoghrd force-pushed the netobserv-2653 branch 2 times, most recently from 551abd2 to d34d7e2 Compare April 8, 2026 15:42
@Amoghrd
Copy link
Copy Markdown
Member Author

Amoghrd commented Apr 8, 2026

/unhold

@Amoghrd
Copy link
Copy Markdown
Member Author

Amoghrd commented Apr 8, 2026

All tests are now passing noo-frontend-tests#44
Failing tests in the job are fixed and passing on rerun.
This is ready for review

@Amoghrd Amoghrd added the needs-review Tells that the PR needs a review label Apr 8, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Collaborator

openshift-ci-robot commented Apr 8, 2026

@Amoghrd: This pull request references NETOBSERV-2689 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 story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Description

Dependencies

#1398

Checklist

  • Does the changes in PR need specific configuration or environment set up for testing?
    • if so please describe it in PR description.
  • I have added thorough unit tests for the change.
  • QE requirements (check 1 from the list):
  • Standard QE validation, with pre-merge tests unless stated otherwise.
  • Regression tests only (e.g. refactoring with no user-facing change).
  • No QE (e.g. trivial change with high reviewer's confidence, or per agreement with the QE team).

Jenkins run: noo-frontend-tests#36
Another run: noo-frontend-tests#41

Summary by CodeRabbit

  • Tests
  • Refined Cypress tests to explicitly open and verify column selection, ensuring selected columns appear in tables.
  • Tightened assertions for time/RTT labels and DNS edge handlers to require numeric millisecond values.
  • Improved cleanup to tolerate already-removed test resources without failing.

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.

@Amoghrd
Copy link
Copy Markdown
Member Author

Amoghrd commented Apr 8, 2026

/retest

1 similar comment
@Amoghrd
Copy link
Copy Markdown
Member Author

Amoghrd commented Apr 8, 2026

/retest

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Apr 8, 2026

@Amoghrd: The following tests 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/plugin-cypress 35f670b link true /test plugin-cypress
ci/prow/qe-e2e-console-tests 35f670b link false /test qe-e2e-console-tests

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.

@memodi
Copy link
Copy Markdown
Member

memodi commented Apr 8, 2026

/lgtm

@memodi
Copy link
Copy Markdown
Member

memodi commented Apr 8, 2026

merging manually since plugin-cypress is failing.

@memodi memodi merged commit cf162d9 into netobserv:main Apr 8, 2026
9 of 12 checks passed
@Amoghrd Amoghrd removed the needs-review Tells that the PR needs a review label Apr 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants