-
Notifications
You must be signed in to change notification settings - Fork 0
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
test for align watermark flow with port configuration #1
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Doron,
- To cover the different scenarios, I suggest using pytest parametrization. It has some advantages comparing to the existing implementation.
- There's no usage of allure step, it would be much more readable to have allure step when running the test with allure reporter.
- Did you consider adding tests to cover the functional correctness of the counters?
0bb802a
to
dcb90a8
Compare
since we agreed to use randomization, didn't use pytest parametrization |
It seems there is missing a test: "Adding a port when watermark is enabled" which is defined in HLD. |
Hi Jibin, Also note that it's not just adding a port now since there was an improvement adding counterpoll flex counters only for ports with queue or pg buffers: sonic-swss 2473 so now it's creating a buffer queue and buffer pg for a certain port and checks the flex counters created for it if needed I can add such a test also for this test here but keep in mind it'll make the test longer than it's now, about 500 seconds after randomization requested by Roy. |
Hi dbarashinvd, |
e34fd19
to
7b4a2b9
Compare
c659c78
to
b89e20d
Compare
Description of PR
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
add a verification test for feature align watermark flow with port configuration
How did you do it?
How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation