[test_techsupport]: Add new test cases for remove password and certs from show techsupport result. #4767
Conversation
|
This pull request introduces 1 alert when merging dd27650 into 54dec75 - view on LGTM.com new alerts:
|
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
| Returns: | ||
| None. | ||
| """ | ||
| skip_release(duthost, ["201811", "201911", "202012", "202106"]) |
There was a problem hiding this comment.
We plan to backport the feature sonic-net/sonic-utilities#1886 to 201911 and later branches. Could you not skip them? #Pending
There was a problem hiding this comment.
Maybe add these back after backport finish?
because if we make the UT run on those branch today, UT will fail and block some PRs.
|
This pull request introduces 1 alert when merging 75399f2 into ce83bca - view on LGTM.com new alerts:
|
|
This pull request introduces 1 alert when merging 4b592a8 into ce83bca - view on LGTM.com new alerts:
|
|
This pull request introduces 1 alert when merging 8fd466b into 94340bb - view on LGTM.com new alerts:
|
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
…from show techsupport result. (sonic-net#4767) ### Description of PR Add new test cases for remove password and certs from show techsupport result. ### Type of change - [ ] Bug fix - [ ] Testbed and Framework(new/improvement) - [x] Test case(new/improvement) ### Back port request ### Approach #### What is the motivation for this PR? Add E2E test case coverage for remove password and certs from show techsupport result. #### How did you do it? Add new E2E test case to cover user scenarios. #### How did you verify/test it? Run new UT make sure they are all pass. Make sure all current UT not break during merge validation. #### Any platform specific information? N/A #### Supported testbed topology if it's a new test case? ### Documentation
Description of PR
Type of change
Back port request
Approach
What is the motivation for this PR?
How did you do it?
Add new E2E test case to cover user scenarios.
How did you verify/test it?
Run new UT make sure they are all pass.
Make sure all current UT not break during merge validation.
Any platform specific information?
N/A
Supported testbed topology if it's a new test case?
Documentation