Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactor(anta.tests): Nicer result failure messages interface(part -1) test module  #1045

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

geetanjalimanegslab
Copy link
Collaborator

@geetanjalimanegslab geetanjalimanegslab commented Feb 18, 2025

Nicer result failure messages Interface test module following testcases are covers.

  1. VerifyInterfaceUtilization
  2. VerifyInterfaceErrors
  3. VerifyInterfaceDiscards
  4. VerifyInterfaceErrDisabled
  5. VerifyInterfacesStatus
  6. VerifyStormControlDrops

Description

Fixes #587

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my code
  • I have run pre-commit for code linting and typing (pre-commit run)
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes (tox -e testenv)

Copy link

codspeed-hq bot commented Feb 18, 2025

CodSpeed Performance Report

Merging #1045 will not alter performance

Comparing geetanjalimanegslab:fix_interface_module_failure_msg (a7aafde) with main (9ba0284)

Summary

✅ 22 untouched benchmarks

@geetanjalimanegslab geetanjalimanegslab changed the title refactor(anta.tests): Nicer result failure messages interface(first 6 test) test module  refactor(anta.tests): Nicer result failure messages interface(part -1) test module  Feb 19, 2025
@vitthalmagadum vitthalmagadum marked this pull request as ready for review February 24, 2025 10:12
Copy link
Contributor

This pull request has conflicts, please resolve those before we can evaluate the pull request.

@@ -653,7 +656,7 @@
"inputs": {"threshold": 70.0},
"expected": {
"result": "failure",
"messages": ["Interface Ethernet1/1 or one of its member interfaces is not Full-Duplex. VerifyInterfaceUtilization has not been implemented."],
"messages": ["Interface: Ethernet1/1 - Interface utilization has not been implemented"],
Copy link
Contributor

Choose a reason for hiding this comment

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

We should keep the mention about is not full-duplex and the test name.

Comment on lines 804 to 807
"messages": [
"Interface: Port-Channel31 MemberInterface: Ethernet3/1 - Not Full-Duplex - Actual: duplexHalf",
"Interface: Port-Channel31 MemberInterface: Ethernet4/1 - Not Full-Duplex - Actual: duplexHalf",
],
Copy link
Contributor

Choose a reason for hiding this comment

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

Same comment as above. I think for this specific use case it's fine to have a single failure message like before.

Copy link
Contributor

Conflicts have been resolved. A maintainer will review the pull request shortly.

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.

Have nicer result failure messages
3 participants