Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit 9d796dd

Browse files
nivi-applewoody-apple
nivi-apple
authored and
woody-apple
committedJul 30, 2024··
Editorial fixes
1 parent f7ef98b commit 9d796dd

File tree

1 file changed

+38
-39
lines changed

1 file changed

+38
-39
lines changed
 

‎src/app/tests/suites/certification/Test_TC_TSTAT_4_2.yaml

+38-39
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ tests:
3838
verification: |
3939
Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE. Below is the log of RPI the result may be vary on the basis of dut implementation.
4040
41-
#2 Test Harness Client attempts to write PresetTypes and gets an INVALID_IN_STATE error since the client didn't send a request to edit the presets by calling StartPresetsSchedulesEditRequest command.
41+
#2 Test Harness Client attempts to write Presets and gets an INVALID_IN_STATE error since the client didn't send a request to edit the presets by calling StartPresetsSchedulesEditRequest command.
4242
./chip-tool thermostat write presets '[ {"presetHandle": "hex:01", "presetScenario": 1, "coolingSetpoint": 2500, "heatingSetpoint": 2600, "builtIn": true }, {"presetHandle": "hex:02", "presetScenario": 2, "coolingSetpoint": 2600, "heatingSetpoint": 2500, "builtIn": true }, {"presetHandle": null, "name": "Sleep", "presetScenario": 3, "coolingSetpoint": 2500, "heatingSetpoint": 2600, "builtIn": false }]' 0x12344321 1
4343
On TH(chip-tool) verify that DUT sends a INVALID_IN_STATE (0xCB)
4444
@@ -86,7 +86,7 @@ tests:
8686
verification: |
8787
Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE. Below is the log of RPI the result may be vary on the basis of dut implementation.
8888
89-
#3b Test Harness Client attempts to write PresetTypes and gets SUCCESS
89+
#3b Test Harness Client attempts to write Presets and gets SUCCESS
9090
9191
./chip-tool thermostat write presets '[ {"presetHandle": "hex:01", "presetScenario": 1, "coolingSetpoint": 2500, "heatingSetpoint": 2600, "builtIn": true }, {"presetHandle": "hex:02", "presetScenario": 2, "coolingSetpoint": 2600, "heatingSetpoint": 2500, "builtIn": true }, {"presetHandle": null, "name": "Sleep", "presetScenario": 3, "coolingSetpoint": 2500, "heatingSetpoint": 2600, "builtIn": false }, {"presetHandle": null, "name": "Wake", "presetScenario": 4, "coolingSetpoint": 2200, "heatingSetpoint": 2900, "builtIn": false }, {"presetHandle": null, "name": "GoingToSleep", "presetScenario": 6, "coolingSetpoint": 2100, "heatingSetpoint": 2500, "builtIn": false }]' 0x12344321 1
9292
On TH(chip-tool) verify that DUT sends a success response
@@ -335,8 +335,8 @@ tests:
335335
value: "y"
336336

337337
- label:
338-
"Step 4a: Test Harness writes to the Presets attribute wherein a
339-
built-in preset is removed"
338+
"Step 4a: Test Harness calls the StartPresetsSchedulesEditRequest
339+
command to edit presets"
340340
PICS: TSTAT.S.F08 && TSTAT.S.C07.Rsp
341341
verification: |
342342
Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE. Below is the log of RPI the result may be vary on the basis of dut implementation.
@@ -365,7 +365,7 @@ tests:
365365
verification: |
366366
Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE. Below is the log of RPI the result may be vary on the basis of dut implementation.
367367
368-
#4b Test Harness Client attempts to write PresetTypes and gets SUCCESS
368+
#4b Test Harness Client attempts to write Presets and gets SUCCESS
369369
370370
./chip-tool thermostat write presets '[ {"presetHandle": "hex:02", "presetScenario": 2, "coolingSetpoint": 2600, "heatingSetpoint": 2500, "builtIn": true }, {"presetHandle": "hex:03", "name": "Sleep", "presetScenario": 3, "coolingSetpoint": 2500, "heatingSetpoint": 2600, "builtIn": false }, {"presetHandle": "hex:04", "name": "Wake", "presetScenario": 4, "coolingSetpoint": 2200, "heatingSetpoint": 2900, "builtIn": false }, {"presetHandle": "hex:06", "name": "GoingToSleep", "presetScenario": 6, "coolingSetpoint": 2100, "heatingSetpoint": 2500, "builtIn": false }]' 0x12344321 1
371371
On TH(chip-tool) verify that DUT sends a success response
@@ -498,9 +498,8 @@ tests:
498498
value: "y"
499499

500500
- label:
501-
"Step 5a: Test Harness writes to the Presets attribute wherein a
502-
preset is removed such that its handle matches the active preset
503-
handle"
501+
"Step 5a: Test Harness calls the SetActivePresetRequest
502+
command to set the active preset handle"
504503
PICS: TSTAT.S.F08 && TSTAT.S.C06.Rsp
505504
verification: |
506505
Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE. Below is the log of RPI the result may be vary on the basis of dut implementation.
@@ -543,7 +542,8 @@ tests:
543542
- name: "expectedValue"
544543
value: "y"
545544

546-
- label: "Step 5c: Test Harness calls StartPresetsSchedulesEditRequest"
545+
- label: "Step 5c: Test Harness calls the StartPresetsSchedulesEditRequest
546+
command to edit presets"
547547
PICS: TSTAT.S.F08 && TSTAT.S.C07.Rsp
548548
verification: |
549549
Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE. Below is the log of RPI the result may be vary on the basis of dut implementation.
@@ -573,7 +573,7 @@ tests:
573573
verification: |
574574
Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE. Below is the log of RPI the result may be vary on the basis of dut implementation.
575575
576-
#5c Test Harness Client attempts to write PresetTypes and gets SUCCESS
576+
#5c Test Harness Client attempts to write Presets and gets SUCCESS
577577
578578
./chip-tool thermostat write presets ./out/debug/chip-tool thermostat write presets '[ {"presetHandle": "hex:01", "presetScenario": 1, "coolingSetpoint": 2500, "heatingSetpoint": 2600, "builtIn": true }, {"presetHandle": "hex:02", "presetScenario": 2, "coolingSetpoint": 2600, "heatingSetpoint": 2500, "builtIn": true }, {"presetHandle": "hex:04", "name": "Wake", "presetScenario": 4, "coolingSetpoint": 2200, "heatingSetpoint": 2900, "builtIn": false }, {"presetHandle": "hex:06", "name": "GoingToSleep", "presetScenario": 6, "coolingSetpoint": 2100, "heatingSetpoint": 2500, "builtIn": false }]' 0x12344321 1
579579
On TH(chip-tool) verify that DUT sends a success response
@@ -723,8 +723,8 @@ tests:
723723
value: "y"
724724

725725
- label:
726-
"Step 6a: Test Harness writes to the Presets attribute wherein a
727-
built-in preset is modified to a non built-in preset"
726+
"Step 6a: Test Harness calls the StartPresetsSchedulesEditRequest
727+
command to edit presets"
728728
PICS: TSTAT.S.F08 && TSTAT.S.C07.Rsp
729729
verification: |
730730
Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE. Below is the log of RPI the result may be vary on the basis of dut implementation.
@@ -754,7 +754,7 @@ tests:
754754
verification: |
755755
Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE. Below is the log of RPI the result may be vary on the basis of dut implementation.
756756
757-
#6b Test Harness Client attempts to write PresetTypes and gets SUCCESS
757+
#6b Test Harness Client attempts to write Presets and gets SUCCESS
758758
759759
./chip-tool thermostat write presets '[ {"presetHandle": "hex:01", "presetScenario": 1, "coolingSetpoint": 2500, "heatingSetpoint": 2600, "builtIn": false }, {"presetHandle": "hex:02", "presetScenario": 2, "coolingSetpoint": 2600, "heatingSetpoint": 2500, "builtIn": true }, {"presetHandle": "hex:03", "name": "Sleep", "presetScenario": 3, "coolingSetpoint": 2500, "heatingSetpoint": 2600, "builtIn": false }, {"presetHandle": "hex:04", "name": "Wake", "presetScenario": 4, "coolingSetpoint": 2200, "heatingSetpoint": 2900, "builtIn": false }, {"presetHandle": "hex:06", "name": "GoingToSleep", "presetScenario": 6, "coolingSetpoint": 2100, "heatingSetpoint": 2500, "builtIn": false }]' 0x12344321 1
760760
On TH(chip-tool) verify that DUT sends a success response
@@ -904,8 +904,8 @@ tests:
904904
value: "y"
905905

906906
- label:
907-
"Step 7a: Test Harness writes to the Presets attribute wherein a new
908-
preset is added with the builtIn flag set to true"
907+
"Step 7a: Test Harness calls the StartPresetsSchedulesEditRequest
908+
command to edit presets"
909909
PICS: TSTAT.S.F08 && TSTAT.S.C07.Rsp
910910
verification: |
911911
Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE. Below is the log of RPI the result may be vary on the basis of dut implementation.
@@ -934,7 +934,7 @@ tests:
934934
verification: |
935935
Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE. Below is the log of RPI the result may be vary on the basis of dut implementation.
936936
937-
#7b Test Harness Client attempts to write PresetTypes and gets SUCCESS
937+
#7b Test Harness Client attempts to write Presets and gets SUCCESS
938938
939939
./chip-tool thermostat write presets '[ {"presetHandle": "hex:01", "presetScenario": 1, "coolingSetpoint": 2500, "heatingSetpoint": 2600, "builtIn": true }, {"presetHandle": "hex:02", "presetScenario": 2, "coolingSetpoint": 2600, "heatingSetpoint": 2500, "builtIn": true }, {"presetHandle": "hex:03", "name": "Sleep", "presetScenario": 3, "coolingSetpoint": 2500, "heatingSetpoint": 2600, "builtIn": false }, {"presetHandle": "hex:04", "name": "Wake", "presetScenario": 4, "coolingSetpoint": 2200, "heatingSetpoint": 2900, "builtIn": false }, {"presetHandle": null, "name": "Vacation", "presetScenario": 5, "coolingSetpoint": 2900, "heatingSetpoint": 2000, "builtIn": true }, {"presetHandle": "hex:06", "name": "GoingToSleep", "presetScenario": 6, "coolingSetpoint": 2100, "heatingSetpoint": 2500, "builtIn": false }]' 0x12344321 1
940940
On TH(chip-tool) verify that DUT sends a success response
@@ -1084,9 +1084,8 @@ tests:
10841084
value: "y"
10851085

10861086
- label:
1087-
"Step 8a: Test Harness writes to the Presets attribute with a preset
1088-
having a non-null preset handle that doesn't exist in the Presets
1089-
attribute"
1087+
"Step 8a: Test Harness calls the StartPresetsSchedulesEditRequest
1088+
command to edit presets"
10901089
PICS: TSTAT.S.F08 && TSTAT.S.C07.Rsp
10911090
verification: |
10921091
Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE. Below is the log of RPI the result may be vary on the basis of dut implementation.
@@ -1116,7 +1115,7 @@ tests:
11161115
verification: |
11171116
Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE. Below is the log of RPI the result may be vary on the basis of dut implementation.
11181117
1119-
#8b Test Harness Client attempts to write PresetTypes and gets SUCCESS
1118+
#8b Test Harness Client attempts to write Presets and gets SUCCESS
11201119
11211120
./chip-tool thermostat write presets '[ {"presetHandle": "hex:01", "presetScenario": 1, "coolingSetpoint": 2500, "heatingSetpoint": 2600, "builtIn": true }, {"presetHandle": "hex:02", "presetScenario": 2, "coolingSetpoint": 2600, "heatingSetpoint": 2500, "builtIn": true }, {"presetHandle": "hex:03", "name": "Sleep", "presetScenario": 3, "coolingSetpoint": 2500, "heatingSetpoint": 2600, "builtIn": false }, {"presetHandle": "hex:04", "name": "Wake", "presetScenario": 4, "coolingSetpoint": 2200, "heatingSetpoint": 2900, "builtIn": false }, {"presetHandle": "hex:08", "name": "GoingToSleep", "presetScenario": 6, "coolingSetpoint": 2100, "heatingSetpoint": 2500, "builtIn": false }]' 0x12344321 1
11221121
On TH(chip-tool) verify that DUT sends a success response
@@ -1266,8 +1265,8 @@ tests:
12661265
value: "y"
12671266

12681267
- label:
1269-
"Step 9a: Test Harness writes to the Presets attribute wherein there
1270-
are 2 presets with the same preset handle"
1268+
"Step 9a: Test Harness calls the StartPresetsSchedulesEditRequest
1269+
command to edit presets"
12711270
PICS: TSTAT.S.F08 && TSTAT.S.C07.Rsp
12721271
verification: |
12731272
Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE. Below is the log of RPI the result may be vary on the basis of dut implementation.
@@ -1294,7 +1293,7 @@ tests:
12941293
verification: |
12951294
Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE. Below is the log of RPI the result may be vary on the basis of dut implementation.
12961295
1297-
#8b Test Harness Client attempts to write PresetTypes and gets SUCCESS
1296+
#8b Test Harness Client attempts to write Presets and gets SUCCESS
12981297
12991298
./chip-tool thermostat write presets '[ {"presetHandle": "hex:01", "presetScenario": 1, "coolingSetpoint": 2500, "heatingSetpoint": 2600, "builtIn": true }, {"presetHandle": "hex:02", "presetScenario": 2, "coolingSetpoint": 2600, "heatingSetpoint": 2500, "builtIn": true }, {"presetHandle": "hex:03", "name": "Sleep", "presetScenario": 3, "coolingSetpoint": 2500, "heatingSetpoint": 2600, "builtIn": false }, {"presetHandle": "hex:03", "name": "Sleep", "presetScenario": 3, "coolingSetpoint": 2500, "heatingSetpoint": 2600, "builtIn": false }, {"presetHandle": "hex:04", "name": "Wake", "presetScenario": 4, "coolingSetpoint": 2200, "heatingSetpoint": 2900, "builtIn": false }, {"presetHandle": "hex:06", "name": "GoingToSleep", "presetScenario": 6, "coolingSetpoint": 2100, "heatingSetpoint": 2500, "builtIn": false }]' 0x12344321 1
13001299
On TH(chip-tool) verify that DUT sends a success response
@@ -1444,8 +1443,8 @@ tests:
14441443
value: "y"
14451444

14461445
- label:
1447-
"Step 10a: Test Harness writes to the Presets attribute wherein a
1448-
built-in preset is modified to be a non built-in preset"
1446+
"Step 10a: Test Harness calls the StartPresetsSchedulesEditRequest
1447+
command to edit presets"
14491448
PICS: TSTAT.S.F08 && TSTAT.S.C07.Rsp
14501449
verification: |
14511450
Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE. Below is the log of RPI the result may be vary on the basis of dut implementation.
@@ -1474,7 +1473,7 @@ tests:
14741473
verification: |
14751474
Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE. Below is the log of RPI the result may be vary on the basis of dut implementation.
14761475
1477-
#10b Test Harness Client attempts to write PresetTypes and gets SUCCESS
1476+
#10b Test Harness Client attempts to write Presets and gets SUCCESS
14781477
14791478
./chip-tool thermostat write presets '[ {"presetHandle": "hex:01", "presetScenario": 1, "coolingSetpoint": 2500, "heatingSetpoint": 2600, "builtIn": false }, {"presetHandle": "hex:02", "presetScenario": 2, "coolingSetpoint": 2600, "heatingSetpoint": 2500, "builtIn": true }, {"presetHandle": "hex:03", "name": "Sleep", "presetScenario": 3, "coolingSetpoint": 2500, "heatingSetpoint": 2600, "builtIn": false }, {"presetHandle": "hex:04", "name": "Wake", "presetScenario": 4, "coolingSetpoint": 2200, "heatingSetpoint": 2900, "builtIn": false }, {"presetHandle": "hex:06", "name": "GoingToSleep", "presetScenario": 6, "coolingSetpoint": 2100, "heatingSetpoint": 2500, "builtIn": false }]' 0x12344321 1
14801479
On TH(chip-tool) verify that DUT sends a success response
@@ -1624,8 +1623,8 @@ tests:
16241623
value: "y"
16251624

16261625
- label:
1627-
"Step 11a: Test Harness writes to the Presets attribute wherein a non
1628-
built-in preset is modified to a built-in preset"
1626+
"Step 11a: Test Harness calls the StartPresetsSchedulesEditRequest
1627+
command to edit presets"
16291628
PICS: TSTAT.S.F08 && TSTAT.S.C07.Rsp
16301629
verification: |
16311630
Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE. Below is the log of RPI the result may be vary on the basis of dut implementation.
@@ -1654,7 +1653,7 @@ tests:
16541653
verification: |
16551654
Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE. Below is the log of RPI the result may be vary on the basis of dut implementation.
16561655
1657-
#11b Test Harness Client attempts to write PresetTypes and gets SUCCESS
1656+
#11b Test Harness Client attempts to write Presets and gets SUCCESS
16581657
16591658
./chip-tool thermostat write presets '[ {"presetHandle": "hex:01", "presetScenario": 1, "coolingSetpoint": 2500, "heatingSetpoint": 2600, "builtIn": true }, {"presetHandle": "hex:02", "presetScenario": 2, "coolingSetpoint": 2600, "heatingSetpoint": 2500, "builtIn": true }, {"presetHandle": "hex:03", "name": "Sleep", "presetScenario": 3, "coolingSetpoint": 2500, "heatingSetpoint": 2600, "builtIn": true }, {"presetHandle": "hex:04", "name": "Wake", "presetScenario": 4, "coolingSetpoint": 2200, "heatingSetpoint": 2900, "builtIn": false }, {"presetHandle": "hex:06", "name": "GoingToSleep", "presetScenario": 6, "coolingSetpoint": 2100, "heatingSetpoint": 2500, "builtIn": false }, {"presetHandle": "hex:06", "name": "GoingToSleep", "presetScenario": 6, "coolingSetpoint": 2100, "heatingSetpoint": 2500, "builtIn": false }]' 0x12344321 1
16601659
On TH(chip-tool) verify that DUT sends a success response
@@ -1804,9 +1803,8 @@ tests:
18041803
value: "y"
18051804

18061805
- label:
1807-
"Step 12a: Test Harness writes to the Presets attribute wherein a
1808-
preset doesn't support names in the PresetTypeFeatures bitmap but has
1809-
a name in the write presets command"
1806+
"Step 12a: Test Harness calls the StartPresetsSchedulesEditRequest
1807+
command to edit presets"
18101808
PICS: TSTAT.S.F08 && TSTAT.S.C07.Rsp
18111809
verification: |
18121810
Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE. Below is the log of RPI the result may be vary on the basis of dut implementation.
@@ -1836,7 +1834,7 @@ tests:
18361834
verification: |
18371835
Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE. Below is the log of RPI the result may be vary on the basis of dut implementation.
18381836
1839-
#11b Test Harness Client attempts to write PresetTypes and gets SUCCESS
1837+
#11b Test Harness Client attempts to write Presets and gets SUCCESS
18401838
18411839
./chip-tool thermostat write presets '[ {"presetHandle": "hex:01", "name": "Occupied", "presetScenario": 1, "coolingSetpoint": 2500, "heatingSetpoint": 2600, "builtIn": true }, {"presetHandle": "hex:02", "presetScenario": 2, "coolingSetpoint": 2600, "heatingSetpoint": 2500, "builtIn": true }, {"presetHandle": "hex:03", "name": "Sleep", "presetScenario": 3, "coolingSetpoint": 2500, "heatingSetpoint": 2600, "builtIn": true }, {"presetHandle": "hex:04", "name": "Wake", "presetScenario": 4, "coolingSetpoint": 2200, "heatingSetpoint": 2900, "builtIn": false }, {"presetHandle": "hex:06", "name": "GoingToSleep", "presetScenario": 6, "coolingSetpoint": 2100, "heatingSetpoint": 2500, "builtIn": false }, {"presetHandle": "hex:06", "name": "GoingToSleep", "presetScenario": 6, "coolingSetpoint": 2100, "heatingSetpoint": 2500, "builtIn": false }]' 0x12344321 1
18421840
On TH(chip-tool) verify that DUT sends a success response
@@ -1988,8 +1986,8 @@ tests:
19881986
#TODO: Add tests for the total number of Presets exceeds the NumberOfPresets supported. Also Add tests for adding presets with preset scenario not present in PresetTypes.
19891987

19901988
- label:
1991-
"Step 13a: Test Harness writes to the Presets attribute but calls
1992-
CancelPresetsSchedulesEditRequest command to cancel the edit request"
1989+
"Step 13a: Test Harness calls the StartPresetsSchedulesEditRequest
1990+
command to edit presets"
19931991
PICS: TSTAT.S.F08 && TSTAT.S.C07.Rsp
19941992
verification: |
19951993
Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE. Below is the log of RPI the result may be vary on the basis of dut implementation.
@@ -2011,12 +2009,13 @@ tests:
20112009
- name: "expectedValue"
20122010
value: "y"
20132011

2014-
- label: "Step 13b: Test Harness writes to the Presets attribute"
2012+
- label: "Step 13b: Test Harness writes to the Presets attribute but calls
2013+
CancelPresetsSchedulesEditRequest command to cancel the edit request"
20152014
PICS: TSTAT.S.F08 && TSTAT.S.A0050
20162015
verification: |
20172016
Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE. Below is the log of RPI the result may be vary on the basis of dut implementation.
20182017
2019-
#13b Test Harness Client attempts to write PresetTypes and gets SUCCESS
2018+
#13b Test Harness Client attempts to write Presets and gets SUCCESS
20202019
20212020
./chip-tool thermostat write presets '[ {"presetHandle": "hex:01", "presetScenario": 1, "coolingSetpoint": 2500, "heatingSetpoint": 2600, "builtIn": true }, {"presetHandle": "hex:02", "presetScenario": 2, "coolingSetpoint": 2600, "heatingSetpoint": 2500, "builtIn": true }, {"presetHandle": "03", "name": "Sleep", "presetScenario": 3, "coolingSetpoint": 2500, "heatingSetpoint": 2600, "builtIn": false }, {"presetHandle": "04", "name": "Wake", "presetScenario": 4, "coolingSetpoint": 2200, "heatingSetpoint": 2900, "builtIn": false }, {"presetHandle": null, "name": "Vacation", "presetScenario": 5, "coolingSetpoint": 2900, "heatingSetpoint": 2000, "builtIn": false }, {"presetHandle": "06", "name": "GoingToSleep", "presetScenario": 6, "coolingSetpoint": 3000, "heatingSetpoint": 1900, "builtIn": false }]' 0x12344321 1
20222021
On TH(chip-tool) verify that DUT sends a success response
@@ -2166,8 +2165,8 @@ tests:
21662165
value: "y"
21672166

21682167
- label:
2169-
"Step 13d: Test Harness reads the Presets attribute without calling
2170-
the CommitPresetsSchedulesRequest command"
2168+
"Step 13d: Test Harness reads the Presets attribute after calling
2169+
the CancelPresetsSchedulesEditRequest command"
21712170
PICS: TSTAT.S.F08 && TSTAT.S.A0050
21722171
verification: |
21732172
Optional Attribute - If it is supported, then in TH log it will results in displaying the value, else it will display UNSUPPORTED_ATTRIBUTE. Below is the log of RPI the result may be vary on the basis of dut implementation.

0 commit comments

Comments
 (0)
Please sign in to comment.