[TC-DD-3.1] Need to print different stages of commissioning flow in the log file as we cant verify all the commissioning flow in the current log file after provision is done

[sowmyassp]

• Problem
  Need to print different stages of commissioning flow in the log file

• expected behavior
  To get all the commissioning flow in the log file after commissioning DUT with TH

• Actual behavior
  Only some of commissioning flow is seen in the current log

• Steps to reproduce
  DUT - sudo ./chip-all-clusters-app --wifi
  TH - ./chip-tool pairing ble-wifi 1 zigbeehome matter123 20202021 3840

• Screenshots, images, logs, etc.
  BLE_provisioning_cntrl.txt
  BLE_provisiong_DUT.txt

• Spec reference
  https://github.com/CHIP-Specifications/connectedhomeip-spec/blob/master/src/service_device_management/CommissioningFlows.adoc

• Test-plan reference
  https://github.com/CHIP-Specifications/chip-test-plans/blob/master/src/devicediscovery.adoc#tc-dd-3-1-commissioning-flow-concurrent-dut-commissionee

[bzbarsky-apple]

@sowmyassp does #14736 address this?

[sowmyassp]

@bzbarsky-apple yes, this ticket addresses the issue

[bzbarsky-apple]

Please close if resolved?

[sowmyassp]

No its not yet resolved, for these [TC-DD-3.1], [TC-DD-3.2], [TC-DD-3.5], [TC-DD-3.6] test-cases we need commissioning flow such as "Commissioner configures Fabric information", "Commissioner requests operational CSR" which is needed to verify this test-cases.

[andy31415]

@sowmyassp - could you describe the reason and use of this printout (likely subset of the actual test case description)?

Release builds of devices (such as devices being certified) would not get access to logs so having tests rely on logs and their content does not seem the best way, however I am not convinced we have an ideal way either. Is there a requirement for certified devices to have logging enabled? How about tiny devices that cannot even have logging (e.g. qpg devices had logging disabled to use less flash).

[cjandhyala]

@andy31415 The log lines requested are on the TH side but not DUT. TCs like https://github.com/CHIP-Specifications/chip-test-plans/blob/3bcd71e5bf2fe7ce7b143614f9b0ee89c9af2b16/src/devicediscovery.adoc#335-tc-dd-35-commissioning-flow---concurrent-dut---commissioner , require to verify every step of the commissioning flow. The only we can do that is by verifying the log lines in the TH to see if DUT finished all those intermediate steps in the commissioning flow. Alternatively we need to think, do we need to verify all those intermediate steps of commissioning flow as part of certification test case OR just verify if the device can be provisioned successfully or not ?

[sowmyassp]

Test-plan is updated with correct commissioning flow and we are getting the same in logs

[sowmyassp]

PFA Logs:
commissioning_cntrl.txt
commissioning_dut.txt