Skip to content

OU-1040: Preliminary Tests + Mock Update#769

Draft
DavidRajnoha wants to merge 15 commits intoopenshift:mainfrom
DavidRajnoha:cypress-incidents-mockin-min-timestamp
Draft

OU-1040: Preliminary Tests + Mock Update#769
DavidRajnoha wants to merge 15 commits intoopenshift:mainfrom
DavidRajnoha:cypress-incidents-mockin-min-timestamp

Conversation

@DavidRajnoha
Copy link
Contributor

No description provided.

DavidRajnoha and others added 15 commits February 5, 2026 10:47
…time display issues

- Add test case for boundary end times not rounded to 5 minutes (OU-1205)
  Interval calculation uses 1-second offsets causing unrounded times like
  "23:29:59" instead of "23:30" in multi-severity incident tooltips

- Add test case for start times mismatch between UI elements (OU-1221)
  Multi-severity incident tooltip start times are 5 minutes off from
  alert tooltip and alerts table values

- Document absolute start date fix implementation using new API call
  (OU-1040)
  Uses min_over_time(timestamp()) instant queries to retrieve actual
  start timestamps regardless of "Last N Days" filter selection
Signed-off-by: Gabriel Bernal <gbernal@redhat.com>
Signed-off-by: Gabriel Bernal <gbernal@redhat.com>
Add support for patching custom cluster-health-analyzer images in COO CSV,
enabling CI jobs on cluster-health-analyzer PRs to run the monitoring-plugin
test suite against custom builds.

- Add update-cha-image.sh script to patch CHA image in COO CSV
- Refactor setupMonitoringConsolePlugin into generic patchCOOCSVImage function
- Add CHA_IMAGE to session key for proper cache invalidation
- Update configure-env.sh with interactive CHA_IMAGE configuration
- Document CYPRESS_CHA_IMAGE usage in README.md
Signed-off-by: Gabriel Bernal <gbernal@redhat.com>
Signed-off-by: Gabriel Bernal <gbernal@redhat.com>
…p fixes

Add regression test (05.reg_15day_data_loading) verifying absolute start
dates remain consistent across "Last N Days" filter changes for ongoing
and escalating-severity incidents (Section 3.4).

Fix mock timestamp generation to align to 5-minute grid matching real
Prometheus query_range step=300 behavior, and use unrounded timestamps
in instant query mocks to surface tooltip date edge cases.

Phase 2 (resolved incident date verification) temporarily disabled
due to alert bar refresh timing issue in the test harness.
@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 12, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 12, 2026

@DavidRajnoha: This pull request references OU-1040 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 bug to target the "4.22.0" version, but no target version was set.

Details

In response to this:

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-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 12, 2026
@openshift-merge-robot
Copy link
Contributor

PR needs rebase.

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.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 12, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 12, 2026

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 12, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: DavidRajnoha
Once this PR has been reviewed and has the lgtm label, please assign jgbernalp for approval. 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

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

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants