-
Notifications
You must be signed in to change notification settings - Fork 727
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 plan for feature Generic Hash #7524
Test plan for feature Generic Hash #7524
Conversation
The pre-commit check detected issues in the files touched by this pull request. For old issues, it is not mandatory to fix them because they were not caused by this change. It is unfair to blame Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
@yxieca could you please help to review or assign? |
@congh-nvidia can you present this test plan in test subgroup meeting? |
Hi @yxieca, could you send me the time of the next test subgroup meeting? |
@congh-nvidia please find the meeting in this calendar: https://sonic-net.github.io/SONiC/Calendar.html |
@nazariig please help to review and also add the feature reviewer |
/azp run Azure.sonic-mgmt |
Azure Pipelines successfully started running 1 pipeline(s). |
The pre-commit check detected issues in the files touched by this pull request. Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
The pre-commit check detected issues in the files touched by this pull request. Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
The pre-commit check detected issues in the files touched by this pull request. Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
The pre-commit check detected issues in the files touched by this pull request. Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
I will update the test plan for the review comments in the Aug 16th sonic-test-workgroup meeting. |
@nazariig please review |
Update the test plan according to the comments in the Aug 16th review meeting: 1. Remove the "doesn't support dualtor" expression. 2. Add clear steps for the lag hash cases when the tested hash field is DST_MAC, ETHERTYPE or VLAN_ID. 3. Add a new test case the cover the lag member remove/add scenario. 4. Remove the test_invalid_hash_fields for it has been covered in the sonic-utilities UT. (https://github.com/sonic-net/sonic-utilities/blob/c7c4831baf2f60c7f63166244eb07c6ab7fe8b8a/tests/hash_test.py)
The pre-commit check detected issues in the files touched by this pull request. Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
The test plan is updated according to the comments in the Aug 16th review meeting:
|
Trim the trailing white line.
The pre-commit check detected issues in the files touched by this pull request. Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
The pre-commit check detected issues in the files touched by this pull request. Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
Hi @yxieca, the pre-commit keeps complaining about the trailing whitespace, but I can't find where it is. Is it auto-fixed by the pre-commit? How can I make the checker pass? |
@congh-nvidia this is a standalone file, have you search for " |
Remove the trailing whitespaces.
As no feedback for sonic test group community and feature owner has approved, moving a head with merging the test plan. |
Description of PR
Summary:
Test plan for the new feature Generic Hash.
The HLD of Generic Hash: sonic-net/SONiC#1101
The test implementation is not included in this PR, will open another PR.
Type of change
Back port request
Approach
What is the motivation for this PR?
Adding the test plan for the new feature Generic Hash.
How did you do it?
How did you verify/test it?
The test plan has already been reviewed internally.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation