OU-1040: Preliminary Tests + Mock Update#769
OU-1040: Preliminary Tests + Mock Update#769DavidRajnoha wants to merge 15 commits intoopenshift:mainfrom
Conversation
…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.
|
@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. DetailsIn 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. |
|
PR needs rebase. DetailsInstructions 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. |
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: DavidRajnoha The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@DavidRajnoha: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
No description provided.