Skip to content
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-SC-3.6] - Reference app required to make DUT as controller #21009

Closed
somu1710 opened this issue Jul 20, 2022 · 6 comments
Closed

[TC-SC-3.6] - Reference app required to make DUT as controller #21009

somu1710 opened this issue Jul 20, 2022 · 6 comments
Assignees
Labels

Comments

@somu1710
Copy link

somu1710 commented Jul 20, 2022

Description:

  • In Secure channel Test case[TC-SC-3.6], requires to verify DUT’s CaseSessionsPerFabric in CapabilityMinima is at least 3 in 5 different fabrics in which each fabric contains 3 reference devices.

  • To execute this test case as it is, requires 15 TH's and one DUT.

  • If we develop the reference app, which can act as a controller, these controllers can be run (bring-up) on the same device to commission the DUT.

  • In a RPI, Connectedhomeip folder, we have Chip-tool, All-clusters-app, lock-app, light-app etc, if these apps can act as a controller, this can send a subscribe message from the same device to the DUT.

  • Our Raspberrypi device [All-cluster-app] does not have an provision to handle this test case.Hence we request for an reference app.

Test case ref:
https://github.com/CHIP-Specifications/chip-test-plans/blob/master/src/securechannel.adoc#tc-sc-3-6-case-resource-validation

  • When the device is acting as controller, we will need to shell access (like chip-tool interact shell) so that we can issue commands/subscribe to the DUT that the controller is going to control
@woody-apple
Copy link
Contributor

Cert Blocker Review: @cjandhyala to follow up with @vivien-apple for possibly how to implement this using the tools we have today.

@tcarmelveilleux
Copy link
Contributor

We already stated elsewhere that a bespoke manner to use a "DUT as a controller" does not go in the spirit of what is required, and actually what we need is just to have N chip-tool clients concurrently, or N python clients concurrently.

There is no arbitrary control path that we could build in less time than using proper means either with chip-tool or Python.

@mrjerryjohns for color about multiple controllers per instance

@woody-apple
Copy link
Contributor

Cert Blocker Review: Marking this as 'needs provisional' unless we have a resolution to this issue today.

@cjandhyala
Copy link
Contributor

Hi @tcarmelveilleux @mrjerryjohns , Could you share the progress on getting the python script to test TC-SC-3.6? The same solution could be used for TC-RR-1.1 and a test step in TC-IDM-4.2 (which also requires having a controller on the same fabric).

@tcarmelveilleux
Copy link
Contributor

I am making extremely good progress on TC-RR-1.1.

I will attempt to start TC-SC-3.6 today.

@woody-apple
Copy link
Contributor

woody-apple commented Aug 16, 2022

SDK Review: We are not taking SDK changes at this point for this test case. Closing, as we believe this is already resolved in master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants