OBSINTA-777: [Incidents] Regression for Charts Display

[DavidRajnoha]

Charts UI Regression Test Coverage

This PR adds regression tests for the Charts UI components on the Incidents page.

The PR is already rebased on #606

I. Tooltip Integrity

The tests ensure tooltips are correctly positioned and provide accurate incident details across various data conditions.

Positioning (Section 2.1)

• Viewport Containment: All tooltips (Incident and Alert charts) remain entirely within the visible viewport.
• Vertical Placement: Tooltips consistently render above the associated bar without any overlap.
• Edge Case Validation: Verifies correct positioning for the topmost (newest) and bottommost (oldest) incidents.

Content (Section 2.1)

• Firing Status: Tooltips for firing incidents correctly display the placeholder --- for the end time.
• Resolved Status: Tooltips for resolved incidents display accurate Start and End timestamps.
• Complexity Handling:
  • Multi-Component: Tooltips correctly list all components involved in the incident.
  • Long Names: Tooltips for incidents with very long alert names (180+ characters) are validated to wrap correctly and maintain viewport containment.

---

II. Chart Bar Rendering and Logic

This section confirms accurate chronological sorting, bar visibility, and functional filtering behavior.

Sorting (Section 2.2)

• Chronological Order: Incidents are correctly sorted, with the newest incident at the top (index 0) and the oldest at the bottom.

Visibility (Section 2.2)

• Short Duration: Incidents with minimal durations (e.g., 10 minutes) are guaranteed to render with a visible width and height greater than zero.
• Opacity: Short-duration bars are confirmed to be visible, not rendered transparently.

Filtering (Section 2.2)

• Y-Axis Spacing: When filters (e.g., severity) are applied, the remaining visible bars maintain their correct vertical spacing (Y-axis positions).

---

III. Time and Severity Visualization

The tests validate the accurate presentation of time formats and the visualization of severity changes.

Date/Time Display (Section 2.3)

• Formatted Times: All timestamps in tooltips and the expanded Alerts Table use the correct, formatted local time.
• Table Status: Start and end times for individual alerts in the Alerts Table accurately reflect their status (timestamp or placeholder text for firing).

Multi-Severity (Section 2.3)

• Segment Rendering: Incident bars that progressed through multiple severities are verified to display the corresponding multiple colored segments.

[openshift-ci-robot]

@DavidRajnoha: This pull request references OBSINTA-777 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.21.0" version, but no target version was set.

In response to this:

Charts UI Regression Test Coverage

This PR adds regression tests for the Charts UI components on the Incidents page.

The PR is already rebased on #606

I. Tooltip Integrity

The tests ensure tooltips are correctly positioned and provide accurate incident details across various data conditions.

Positioning (Section 2.1)

• Viewport Containment: All tooltips (Incident and Alert charts) remain entirely within the visible viewport.
• Vertical Placement: Tooltips consistently render above the associated bar without any overlap.
• Edge Case Validation: Verifies correct positioning for the topmost (newest) and bottommost (oldest) incidents.

Content (Section 2.1)

• Firing Status: Tooltips for firing incidents correctly display the placeholder --- for the end time.
• Resolved Status: Tooltips for resolved incidents display accurate Start and End timestamps.
• Complexity Handling:
  • Multi-Component: Tooltips correctly list all components involved in the incident.
  • Long Names: Tooltips for incidents with very long alert names (180+ characters) are validated to wrap correctly and maintain viewport containment.

---

II. Chart Bar Rendering and Logic

This section confirms accurate chronological sorting, bar visibility, and functional filtering behavior.

Sorting (Section 2.2)

• Chronological Order: Incidents are correctly sorted, with the newest incident at the top (index 0) and the oldest at the bottom.

Visibility (Section 2.2)

• Short Duration: Incidents with minimal durations (e.g., 10 minutes) are guaranteed to render with a visible width and height greater than zero.
• Opacity: Short-duration bars are confirmed to be visible, not rendered transparently.

Filtering (Section 2.2)

• Y-Axis Spacing: When filters (e.g., severity) are applied, the remaining visible bars maintain their correct vertical spacing (Y-axis positions).

---

III. Time and Severity Visualization

The tests validate the accurate presentation of time formats and the visualization of severity changes.

Date/Time Display (Section 2.3)

• Formatted Times: All timestamps in tooltips and the expanded Alerts Table use the correct, formatted local time.
• Table Status: Start and end times for individual alerts in the Alerts Table accurately reflect their status (timestamp or placeholder text for firing).

Multi-Severity (Section 2.3)

• Segment Rendering: Incident bars that progressed through multiple severities are verified to display the corresponding multiple colored segments.

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]

[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 kyoto for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[falox]

/label qe-approved

[falox]

/label ux-approved

[openshift-ci-robot]

@DavidRajnoha: This pull request references OBSINTA-777 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.21.0" version, but no target version was set.

In response to this:

Charts UI Regression Test Coverage

This PR adds regression tests for the Charts UI components on the Incidents page.

The PR is already rebased on #606

I. Tooltip Integrity

The tests ensure tooltips are correctly positioned and provide accurate incident details across various data conditions.

Positioning (Section 2.1)

• Viewport Containment: All tooltips (Incident and Alert charts) remain entirely within the visible viewport.
• Vertical Placement: Tooltips consistently render above the associated bar without any overlap.
• Edge Case Validation: Verifies correct positioning for the topmost (newest) and bottommost (oldest) incidents.

Content (Section 2.1)

• Firing Status: Tooltips for firing incidents correctly display the placeholder --- for the end time.
• Resolved Status: Tooltips for resolved incidents display accurate Start and End timestamps.
• Complexity Handling:
  • Multi-Component: Tooltips correctly list all components involved in the incident.
  • Long Names: Tooltips for incidents with very long alert names (180+ characters) are validated to wrap correctly and maintain viewport containment.

---

II. Chart Bar Rendering and Logic

This section confirms accurate chronological sorting, bar visibility, and functional filtering behavior.

Sorting (Section 2.2)

• Chronological Order: Incidents are correctly sorted, with the newest incident at the top (index 0) and the oldest at the bottom.

Visibility (Section 2.2)

• Short Duration: Incidents with minimal durations (e.g., 10 minutes) are guaranteed to render with a visible width and height greater than zero.
• Opacity: Short-duration bars are confirmed to be visible, not rendered transparently.

Filtering (Section 2.2)

• Y-Axis Spacing: When filters (e.g., severity) are applied, the remaining visible bars maintain their correct vertical spacing (Y-axis positions).

---

III. Time and Severity Visualization

The tests validate the accurate presentation of time formats and the visualization of severity changes.

Date/Time Display (Section 2.3)

• Formatted Times: All timestamps in tooltips and the expanded Alerts Table use the correct, formatted local time.
• Table Status: Start and end times for individual alerts in the Alerts Table accurately reflect their status (timestamp or placeholder text for firing).

Multi-Severity (Section 2.3)

• Segment Rendering: Incident bars that progressed through multiple severities are verified to display the corresponding multiple colored segments.

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.

[DavidRajnoha]

/retest

[openshift-ci]

@DavidRajnoha: 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/okd-scos-e2e-aws-ovn	6ee8b74	link	false	/test okd-scos-e2e-aws-ovn

Full PR test history. Your PR dashboard.

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.