[SVE] TC-MCORE-FS-1.3: Timeout too low for device discovery & commissioning from DUT

[samadDotDev]

Reproduction steps

In TC-MCORE-FS-1.3, a TH_SERVER_NO_UID (an example app with no unique ID) is commissioned onto TH's fabric, and DUT_FSA's aggregator parts list is checked before the commissioning window on TH_SERVER_NO_UID is opened using TH's fabric (this is in response to CommissionerControlCluster::CommissionNode command as part of reverse commissioning between TH and DUT). Right after that, the DUT is expected to discover and commission TH_SERVER_NO_UID and just 2s after that, the DUT's parts list is reread to determine whether the new device has been made available as a bridged node.

This timeout is pretty short because right after issuing the CommissionerControlCluster::ReverseOpenCommissioningWindow command, the DUT is expected to discover the newly advertised _matterc._udp service, resolve its address, establish PASE, install the DUT_FSA's fabric, subscribe (& perform other necessary interactions during onboarding) before making it available as a newly accessible bridged node on the DUT_FSA's aggregator parts list, and some of these operations can take a bit of time.

Bug prevalence

Almost always on our DUT

GitHub hash of the SDK that was being used

56c0bd8

Platform

other

Platform Version(s)

No response

Type

Test Improvement

Testing

Hardware validated, Platform validated

(Optional) If manually tested please explain why this is only manually tested

No response

Anything else?

No response

[cjandhyala]

@samadDotDev can you update the PR with the comments ?