[Kubernetes] Testplan Document #2299
Conversation
|
retest this please |
|
retest vsimage please |
wangxin
left a comment
There was a problem hiding this comment.
I understand that this is a work in progress. But it would be better if the test plan can have information about how to:
- prepare docker images before test
- prepare and update manifest for each test
docs/K8s-test-plan.md
Outdated
| Verify Device Under Test (DUT) running kube mode feature container v1.1.1 properly upgrades to kube mode feature v2.0.0 upon successful application of v2.0.0 manifest. | ||
| #### Test Configuration | ||
| - Pick up from step 3 of [TC_LOCAL_KUBE_1](#tc_local_kube_1-switch-between-local-mode-and-kube-mode) | ||
| - {feature x} `current_owner=kube`, `set_owner=kube`, `remote_state=running`, `container_version=1.1.1` |
There was a problem hiding this comment.
According to Kubernetes support, only set_owner=kube is configuration. Other items are status of DUT or feature. Probably it is better to explicitly specify what is required configuration and what is required status as precondition of a test.
There was a problem hiding this comment.
Thanks for the feedback, I updated the document to distinguish between desired status and configuration in Test Setup.
docs/K8s-test-plan.md
Outdated
| #### Test Objective | ||
| Verify Device Under Test (DUT) responds appropriately to kube server `disable` flag by joining master when `disable=false` and resetting from master when `disable=true`. | ||
| #### Test Configuration | ||
| - Pick up from step 6 of [TC_JOIN_1](#tc_join_1-join-master-once-available) |
There was a problem hiding this comment.
Describing test configuration like this makes the test cases dependent on other test cases. It would be more clear if the test cases can be relatively independent. Can you consider describing the preconditions of each test in a more independent way? Like briefly describe what is the required state and configuration to start each test.
There was a problem hiding this comment.
I see why this description format makes it seem like some test cases depend on other test cases. I described it with "pick up from {another test case}" to make the test steps less wordy/redundant, and focus on what is being tested in the test case. In the actual test code, there will be no dependence on other test cases.
Based on your feedback, I changed the Test Configuration header to Test Setup and describe the desired status and configuration of the DUT, features, Kubernetes server.
To keep the test steps more concise, is it okay to say "To get to desired Test Setup state, pick up from {another test case}" after describing the required status and configuration for Test Setup?
docs/K8s-test-plan.md
Outdated
| Verify Device Under Test (DUT) local mode feature properly responds to `set_owner=kube` when kube mode feature fails to deploy properly (failed manifest application due to invalid URL). Local mode container should keep running until kube mode feature is successfully deployed. | ||
| #### Test Configuration | ||
| - Pick up from step 6 of [TC_JOIN_1](#tc_join_1-join-master-once-available) | ||
| - {feature x} `current_owner=local`, `set_owner=kube`, `remote_state=none`, `container_version=1.0.0` |
There was a problem hiding this comment.
Can you add a section before the steps to describe how to change the configuration, how to check the DUT and feature status?
There was a problem hiding this comment.
Yes, I have added this to the description of the statuses and configurations. Please let me know if I should adjust the placement
wangxin
left a comment
There was a problem hiding this comment.
It looks like your later changes introduced conflicts. Could you resolve the conflicts?
|
@isabelmsft, can you resolve the conflict and merge the test plan doc? |
|
@isabelmsft please solve the merge conflict. |
…submodule head (sonic-net#11705) Kernel: * 86c4b66 2022-07-28 | [Mellanox] Add new kernel patches from HW-MGMT package V.7.0020.3005 (sonic-net#287) (HEAD -> 202205) [Kebo Liu] * 3a8416a 2022-07-05 | [patch] mlxsw: i2c: Prevent transaction execution for special chip (sonic-net#279) [Stepan Blyshchak] swss: * 3f69944 2022-08-10 | Set internal class state to reflect the actual state (sonic-net#2410) (HEAD -> 202205, tag: foo) [Prince Sunny] * 87e98eb 2022-08-09 | [portsorch] Expose supported FEC modes to STABE_DB and check whether FEC mode is supported before setting it (sonic-net#2400) [Stephen Sun] * e71ab99 2022-07-29 | portsorch: initial support for link-training (sonic-net#2359) [Dante (Kuo-Jung) Su] * ed5e5be 2022-07-08 | Port configuration incremental update support (sonic-net#2305) [Junchao-Mellanox] utilities: * 0df3ba8 2022-08-12 | Revert "Improve the way to check port type of RJ45 port (sonic-net#2249)" (HEAD -> 202205) [Ying Xie] * 9b21903 2022-08-12 | Fix test failure in dump table test in 202205 (sonic-net#2307) (HEAD -> 202205, github/202205) [Stephen Sun] * 750d1db 2022-08-11 | Convert IPv6 addresses to lowercase in apply-patch (sonic-net#2299) (HEAD -> 202205) [dbarashinvd] * 555947e 2022-08-09 | [config][muxcable] add support to enable/disable ycable telemetry (sonic-net#2297) [vdahiya12] * 978f416 2022-08-09 | Fix GCU bug when backend service modifying config (sonic-net#2295) [jingwenxie] * 8fed381 2022-08-02 | [intfutil] Check whether the FEC mode is supported on the platform before configuring it to CONFIG_DB (sonic-net#2223) (github/202205) [Stephen Sun] * a1a09e4 2022-07-29 | Improve the way to check port type of RJ45 port (sonic-net#2249) [Stephen Sun] * 9bdbfb8 2022-05-19 | sonic-utils: initial support for link-training (sonic-net#2071) [Dante (Kuo-Jung) Su] * c088ec4 2022-08-10 | Support to enable fips for the command sonic_installer (sonic-net#2154) (sonic-net#2303) [xumia] platform-daemon: * 767cfb6 2022-08-09 | [ycabled] add capability to enable/disable telemetry (sonic-net#279) (HEAD -> 202205) [vdahiya12] linkmgrd: * cf1ba2b 2022-08-12 | wait for handler to be completed (sonic-net#114) (HEAD -> 202205, github/202205) [Jing Zhang] * e99026c 2022-08-11 | [lgtm]: add uuid-dev to lgtm prepare (sonic-net#112) (HEAD -> 202205) [Jing Zhang] * bd1b7f0 2022-08-11 | Adjust `DbInterfaceRaceConditionCheck` to Wait Longer for Handlers to be executed (sonic-net#111) (HEAD -> 202205, github/202205) [Jing Zhang] * e9dc6b2 2022-08-11 | Backoff mux probing for server down scenario (sonic-net#106) [Jing Zhang] * 0d61171 2022-08-09 | Fix race condition caused by strand `wrap` method (sonic-net#104) [Jing Zhang] * e9ede7d 2022-07-02 | Enforce switch after config mux to active (sonic-net#95) [Longxiang Lyu] * 15dbc30 2022-06-30 | Add unittest to verify mux toggle active (sonic-net#94) [Longxiang Lyu] Signed-off-by: Ying Xie <ying.xie@microsoft.com>
…net#14462) Why I did it src/linkmgrd * 373544f - (HEAD -> 202205, origin/202205) [active-active] Add mux server state correction mechanism (sonic-net#191) (3 days ago) [Longxiang Lyu] src/sonic-platform-daemons * 0260695 - (HEAD -> 202205, origin/202205) Fix issue: Exception occured at SfpStateUpdateTask thread due to KeyError('status') (sonic-net#346) (3 days ago) [Junchao-Mellanox] src/sonic-swss * af46930 - (HEAD -> 202205, origin/202205) Custom monitoring based priority tunnels (3 days ago) [siqbal1986] src/sonic-utilities * fe224f09 - (HEAD -> 202205, origin/202205) Revert "Convert IPv6 addresses to lowercase in apply-patch (sonic-net#2299)" (sonic-net#2758) (3 days ago) [jingwenxie] * cf12bb5e - [warm-reboot] Use kexec_file_load instead of kexec_load when available (sonic-net#2608) (10 days ago) [Saikrishna Arcot] * 93f1d740 - [warm-reboot] fix warm-reboot when /tmp/cache is missing (sonic-net#2367) (10 days ago) [Stepan Blyshchak]
Kubernetes testplan in progress