open-commissioning-window commands in test scripts not spec compliant

[agners]

Problem

Several instructions in test YAML files suggest a chip-tool pairing open-commissioning-window command with not spec compliant timeout of 100s (instead of 180s).

$ grep -r -e "pairing open-commissioning-window [0-9]* [0-9]* 100" src
src/app/tests/suites/certification/Test_TC_MF_1_21.yaml:          ./chip-tool pairing open-commissioning-window 1 1 100 1000 3840
src/app/tests/suites/certification/Test_TC_MF_1_16.yaml:          ./chip-tool pairing open-commissioning-window 1 1 100 1000 3840
src/app/tests/suites/certification/Test_TC_MF_1_16.yaml:          ./chip-tool pairing open-commissioning-window 1 1 100 1000 3840
src/app/tests/suites/certification/Test_TC_MF_1_16.yaml:          ./chip-tool pairing open-commissioning-window 1 1 100 1000 3840
src/app/tests/suites/certification/Test_TC_MF_1_16.yaml:          ./chip-tool pairing open-commissioning-window 1 1 100 1000 3840
src/app/tests/suites/certification/Test_TC_MF_1_16.yaml:          ./chip-tool pairing open-commissioning-window 1 1 100 1000 3840
src/app/tests/suites/certification/Test_TC_MF_1_16.yaml:          ./chip-tool pairing open-commissioning-window 1 1 100 1000 3840
src/app/tests/suites/certification/Test_TC_MF_1_16.yaml:          ./chip-tool pairing open-commissioning-window 1 1 100 1000 3840
src/app/tests/suites/certification/Test_TC_MF_1_13.yaml:          ./chip-tool pairing open-commissioning-window 1 1 100 1000 3840
src/app/tests/suites/certification/Test_TC_MF_1_13.yaml:          ./chip-tool pairing open-commissioning-window 1 1 100 1000 3840
src/app/tests/suites/certification/Test_TC_MF_1_13.yaml:          ./chip-tool pairing open-commissioning-window 1 1 100 1000 3840
src/app/tests/suites/certification/Test_TC_MF_1_13.yaml:          ./chip-tool pairing open-commissioning-window 1 1 100 1000 3840
src/app/tests/suites/certification/Test_TC_MF_1_19.yaml:          ./chip-tool pairing open-commissioning-window 1 1 100 1000 3840
src/app/tests/suites/certification/Test_TC_MF_1_19.yaml:          ./chip-tool pairing open-commissioning-window 1 1 100 1000 3840
src/app/tests/suites/certification/Test_TC_MF_1_23.yaml:          ./chip-tool pairing open-commissioning-window 1 1 100 1000 3840
src/app/tests/suites/certification/Test_TC_MF_1_17.yaml:          ./chip-tool pairing open-commissioning-window 1 1 100 1000 3840
src/app/tests/suites/certification/Test_TC_MF_1_17.yaml:          ./chip-tool pairing open-commissioning-window 1 1 100 1000 3840
src/app/tests/suites/certification/Test_TC_MF_1_14.yaml:          ./chip-tool pairing open-commissioning-window 1 1 100 1000 3840
src/app/tests/suites/certification/Test_TC_MF_1_14.yaml:          ./chip-tool pairing open-commissioning-window 1 1 100 1000 3840
src/app/tests/suites/certification/Test_TC_MF_1_14.yaml:          ./chip-tool pairing open-commissioning-window 1 1 100 1000 3840
src/app/tests/suites/certification/Test_TC_MF_1_14.yaml:          ./chip-tool pairing open-commissioning-window 1 1 100 1000 3840
src/app/tests/suites/certification/Test_TC_MF_1_7.yaml:          ./chip-tool pairing open-commissioning-window 1 1 100 1000 3840
src/app/tests/suites/certification/Test_TC_MF_1_7.yaml:          ./chip-tool pairing open-commissioning-window 1 1 100 1000 3840

Proposed Solution

Increase the value to 180s (unless the test case is about validating for failure).

[bzbarsky-apple]

Please file an issue in https://github.com/CHIP-Specifications/chip-test-plans/ ...

@cjandhyala @manjunath-grl can we get these test scripts fixed, please?

[agners]

Created a spec issue https://github.com/CHIP-Specifications/chip-test-plans/issues/1432

[bzbarsky-apple]

@manjunath-grl test script has been updated. Please fix the YAML?

[manjunath-grl]

@bzbarsky-apple the above mentioned testcases are Manual scripts, the validation sheet has been update we will update the scripts as per the sheet and make PR

[kowsisoundhar12]

@bzbarsky-apple @agners updated above listed MF scripts,pls refer following PR's 20227,20127

[agners]

LGTM.