-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
TC-TCTL-2.3 python test #36703
TC-TCTL-2.3 python test #36703
Conversation
Changed Files
|
PR #36703: Size comparison from 2bc3251 to 71708d1 Full report (69 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
…ttribute_check_success()
PR #36703: Size comparison from 2bc3251 to cb1fdfc Full report (69 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
PR #36703: Size comparison from af8d173 to 5777abd Full report (69 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
PR #36703: Size comparison from b0d0614 to 7fa71d7 Full report (19 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, nrfconnect, qpg, stm32, tizen)
|
PR #36703: Size comparison from b0d0614 to 1a8d6b2 Full report (69 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
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.
Left two suggestions. That second one is totally my fault - should have realized that earlier. My apologies.
With those changes, this PR looks good, so just ping me once those changes are done and I can checkmark this.
The other thing that will need to happen here is an update to the test plan to remove the PICS markings. Once you add the expected outcome strings, we have a script that can dump the test plan table, so it's just a copy-paste, open PR thing.
The test plan generation script is here: https://github.com/project-chip/connectedhomeip/blob/master/src/python_testing/test_plan_table_generator.py
You just give the file name, class name and test name. So that would be
python src/python_testing/test_plan_table_generator.py TC_TCTL_2_3.py TC_TCTL_2_3 test_TC_TCTL_2_3
A bit redundant, but oh well.
The test plan is here: https://github.com/CHIP-Specifications/chip-test-plans/blob/master/src/cluster/temperaturecontrol.adoc#tc-tctl-2-3-optional-temperature-level-attributes-with-dut_server
You would just replace the table in the "Test Procedure" section with the one that's generated, and open a PR saying that you're removing the PICS markers because those attributes are mandatory when the TL feature is supported.
PR #36703: Size comparison from b0d0614 to 0daf2a1 Full report (69 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
I've made a requested changes and asked Juan to raise a PR to a test plan repo https://github.com/CHIP-Specifications/chip-test-plans/pull/4834 as I still have to get access to CHIP-Specifications organization |
PR #36703: Size comparison from dedef1f to c325a1e Full report (70 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
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.
LGTM
* implement TC_TCTL_2_3 in Python * add test to CI workflow * revert incorrect path addition, leave only xml parsing check * fix typo * fix code review comment: rework reading attribute using read_single_attribute_check_success() * use run_if_endpoint_matches decorator and use attribute guards * reuse cluster variable * address code review comments * fix typos * fix loop issue found in review
Category:
Functional
Description:
Verifies that the DUT can respond to Temperature Control Cluster attribute read commands. This test case is required only if the TL feature is supported (TCTL.S.F01(TL)). Some check examples:
Test plan for more details: https://github.com/CHIP-Specifications/chip-test-plans/blob/master/src/cluster/temperaturecontrol.adoc#tc-tctl-2-3-optional-temperature-level-attributes-with-dut_server