FPD Status Test Implementation for Cisco Using Functional Translator#5242
FPD Status Test Implementation for Cisco Using Functional Translator#5242RishabhAgarwal-2001 wants to merge 2 commits intomainfrom
Conversation
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request introduces a new test to validate the FPD status translation for Cisco devices. It establishes a robust mechanism to query FPD status using OpenConfig paths by first discovering native FPD names and then applying a functional translator to retrieve and verify their operational state. Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. Footnotes
|
Pull Request Functional Test Report for #5242 / ebc4eaaVirtual Devices
Hardware Devices
|
|
@RishabhAgarwal-2001 This pr is in progress to move these tests to correct folder: |
There was a problem hiding this comment.
Code Review
The pull request introduces a new test for Cisco FPD status using a functional translator, along with the necessary updates to the deviation mechanism. The implementation correctly integrates the new functional translator and adheres to the established patterns for platform-specific deviations. No critical, high, or medium severity issues were identified in the changes.
No description provided.