Move all paltform test conditional marks to tests_mark_conditions_platform_tests.yaml. #14370
Conversation
|
Is it possible to add some PR check to avoid people add platform testcases in |
Good suggestion! Maybe we can add some checks in Pre_test Static Analysis. |
opcoder0
left a comment
There was a problem hiding this comment.
LGTM. Just a minor comment on the closed issue.
| platform_tests/test_auto_negotiation.py: | ||
| skip: | ||
| reason: "auto negotiation test highly depends on test enviroments, file issue to track and skip for now" | ||
| conditions: https://github.com/sonic-net/sonic-mgmt/issues/5447 |
There was a problem hiding this comment.
This issue is closed. Will this still be skipped?
There was a problem hiding this comment.
If issue is closed, then testcase will not be skipped.
…yaml` (sonic-net#14370) What is the motivation for this PR? We have a specific yaml file tests/common/plugins/conditional_mark/tests_mark_conditions_platform_tests.yaml to record the conditional marks of platfrom test. In this PR, we move all the conditional marks of platform test in tests_mark_conditions.yaml to its specific yaml file. And if the key of conditional mark is repetitive in these two files, we combine them together. How did you do it? Move all paltform test conditional marks to tests_mark_conditions_platform_tests.yaml and combine the repetitive keys.
…yaml` (sonic-net#14370) What is the motivation for this PR? We have a specific yaml file tests/common/plugins/conditional_mark/tests_mark_conditions_platform_tests.yaml to record the conditional marks of platfrom test. In this PR, we move all the conditional marks of platform test in tests_mark_conditions.yaml to its specific yaml file. And if the key of conditional mark is repetitive in these two files, we combine them together. How did you do it? Move all paltform test conditional marks to tests_mark_conditions_platform_tests.yaml and combine the repetitive keys.
|
@yutongzhang-microsoft PR conflicts with 202205 branch |
|
@yutongzhang-microsoft PR conflicts with 202311 branch |
|
@yutongzhang-microsoft PR conflicts with 202012 branch |
|
@yutongzhang-microsoft PR conflicts with 202405 branch |
|
@yutongzhang-microsoft PR conflicts with 202305 branch |
…yaml` (sonic-net#14370) What is the motivation for this PR? We have a specific yaml file tests/common/plugins/conditional_mark/tests_mark_conditions_platform_tests.yaml to record the conditional marks of platfrom test. In this PR, we move all the conditional marks of platform test in tests_mark_conditions.yaml to its specific yaml file. And if the key of conditional mark is repetitive in these two files, we combine them together. How did you do it? Move all paltform test conditional marks to tests_mark_conditions_platform_tests.yaml and combine the repetitive keys.
…et#17179) * Revert "[202205] [Mellanox] Fix issue: user must set admin down before toggling LPM (sonic-net#14370)" This reverts commit f74c69e. * update copyright header Signed-off-by: Kebo Liu <kebol@nvidia.com>
Description of PR
We have a specific yaml file
tests/common/plugins/conditional_mark/tests_mark_conditions_platform_tests.yamlto record the conditional marks of platfrom test. In this PR, we move all the conditional marks of platform test intests_mark_conditions.yamlto its specific yaml file. And if the key of conditional mark is duplicate in these two files, we combine them together.Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
We have a specific yaml file
tests/common/plugins/conditional_mark/tests_mark_conditions_platform_tests.yamlto record the conditional marks of platfrom test. In this PR, we move all the conditional marks of platform test intests_mark_conditions.yamlto its specific yaml file. And if the key of conditional mark is repetitive in these two files, we combine them together.How did you do it?
Move all paltform test conditional marks to
tests_mark_conditions_platform_tests.yamland combine the repetitive keys.How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation