Skip to content

Add DOM post-test deviation attributes, telemetry profiling TC#23356

Open
mihirpat1 wants to merge 5 commits intosonic-net:masterfrom
mihirpat1:dom-deviation-attrs-telemetry-tc
Open

Add DOM post-test deviation attributes, telemetry profiling TC#23356
mihirpat1 wants to merge 5 commits intosonic-net:masterfrom
mihirpat1:dom-deviation-attrs-telemetry-tc

Conversation

@mihirpat1
Copy link
Copy Markdown
Contributor

@mihirpat1 mihirpat1 commented Mar 26, 2026

Description of PR

Summary:
Add post-test deviation validation attributes, a new telemetry update interval profiling test case, and clarify prerequisite failure behavior in DOM and system test plans.

Type of change

  • Bug fix
  • Testbed and Framework(new/improvement)
  • New Test case
    • Skipped for non-supported platforms
  • Test case improvement

Back port request

  • 202205
  • 202305
  • 202311
  • 202405
  • 202411
  • 202505
  • 202511

Approach

What is the motivation for this PR?

Tests that restore the port to steady-state operation (e.g., interface shutdown/startup, DOM polling toggle) had no way to verify that sensor readings returned to acceptable levels. Additionally, there was no test to profile DOM telemetry update intervals for cross-release regression detection. Finally, the prerequisite failure behavior was undocumented.

How did you do it?

Please refer to the HLD diff

How did you verify/test it?

Documentation-only change — reviewed for internal consistency across attribute table, example JSON, post-test deviation rule, and test case steps/expected results.

Any platform specific information?

N/A — deviation attributes are optional and configured per-transceiver in dom.json.

Supported testbed topology if it's a new test case?

N/A — test plan documentation update only.

Documentation

Updated docs/testplan/transceiver/dom_test_plan.md and docs/testplan/transceiver/system_test_plan.md.

MSFT ADO - 37280302

@mihirpat1 mihirpat1 requested a review from Copilot March 26, 2026 20:15
@mssonicbld
Copy link
Copy Markdown
Collaborator

/azp run

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Updates the transceiver DOM and system test plan documentation to add configurable post-test deviation validation attributes and define a new telemetry update interval profiling test case, while clarifying prerequisite failure behavior.

Changes:

  • Documented new DOM post-test deviation attributes (upper/lower bounds) and added a post-test deviation validation rule.
  • Added a new “Telemetry update interval profiling” advanced DOM test case with configurable polling interval/duration attributes.
  • Clarified prerequisite-test failure semantics in both DOM and system test plans.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File Description
docs/testplan/transceiver/dom_test_plan.md Adds new post-test deviation attributes/rule, updates dom.json example, expands advanced test cases, and introduces telemetry update interval profiling TC.
docs/testplan/transceiver/system_test_plan.md Adds a note documenting how prerequisite test case failures affect dependent system test cases.

@mssonicbld
Copy link
Copy Markdown
Collaborator

/azp run

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

@mssonicbld
Copy link
Copy Markdown
Collaborator

/azp run

mihirpat1 and others added 3 commits March 26, 2026 20:58
Signed-off-by: Mihir Patel <patelmi@microsoft.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Signed-off-by: Mihir Patel <patelmi@microsoft.com>
Signed-off-by: Mihir Patel <patelmi@microsoft.com>
@mihirpat1 mihirpat1 force-pushed the dom-deviation-attrs-telemetry-tc branch from b7696fb to 1743d52 Compare March 26, 2026 20:58
@mssonicbld
Copy link
Copy Markdown
Collaborator

/azp run

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

Signed-off-by: Mihir Patel <patelmi@microsoft.com>
@mssonicbld
Copy link
Copy Markdown
Collaborator

/azp run

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.

| telemetry_profile_poll_interval_sec | integer | 10 | O | transceivers or platform_hwsku_overrides | Polling interval in seconds for the telemetry update profiling test |
| telemetry_profile_duration_min | integer | 10 | O | transceivers or platform_hwsku_overrides | Duration in minutes to run the telemetry update profiling test |

**Post-test range rule:** For tests that restore a port to steady-state operation, verify each post-test DOM reading falls within its configured `{"min", "max"}` range. The check applies only to attributes that are present in the configuration (`min <= post-test value <= max`). Lane-based entries such as TX bias and TX/RX power use the `LANE_NUM` expansion and are validated per lane. The test fails if any enabled field falls outside its configured range.
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

It would be good to clarify that the post-check is looking for relative changes based on the first (or average) measurement. Something like min <= post-test value - first-read value <= max

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@bfoo-msft Addressed this now

"MMA1T00-VS-400G": {
"temperature_threshold_range": {"lowalarm": -30.0, "lowwarning": -10.0, "highwarning": 75.0, "highalarm": 85.0}
"temperature_threshold_range": {"lowalarm": -30.0, "lowwarning": -10.0, "highwarning": 75.0, "highalarm": 85.0},
"voltage_deviation_range": {"min": 3.25, "max": 3.45},
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

These thresholds use absolute values, not relative values.
Suggestions are:
"voltage_deviation_range": {"min": -0,2, "max": 0,2},
"laser_temperature_deviation_range": {"min": -10, "max": 10},
"txLANE_NUMbias_deviation_range": {"min": -5, "max": 5},
"txLANE_NUMpower_deviation_range": {"min": -0.2, "max": 0.2},
"rxLANE_NUMpower_deviation_range": {"min": -0.5, "max": 0.5}

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@bfoo-msft Addressed this now

Signed-off-by: Mihir Patel <patelmi@microsoft.com>
@mssonicbld
Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines could not run because the pipeline triggers exclude this branch/path.

@yxieca
Copy link
Copy Markdown
Collaborator

yxieca commented Mar 28, 2026

AI agent on behalf of Ying.\n\nI found issues that need attention.\n\n

Copy link
Copy Markdown
Collaborator

@yxieca yxieca left a comment

Choose a reason for hiding this comment

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

AI agent on behalf of Ying. Reviewed; no issues found.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants