[Bug] How to generate NOC chain according to TC-OPCREDS testcases?

project-chip / certification-tool

A test harness and tooling designed to simplify development, testing, and certification for devices, guided by the Connectivity Standards Alliance.

https://csa-iot.org/

Apache License 2.0

36 stars 22 forks source link

[Bug] How to generate NOC chain according to TC-OPCREDS testcases? #134

Open Yinxq opened 8 months ago

Yinxq commented 8 months ago

Describe the bug

According to TC-OPCREDS-3.1, TC-OPCREDS-3.4 and TC-OPCREDS-3.5, TH needs to obtain or generate the NOC chain using the CSR elements from the previous step. How should I get or generate NOC chain?

Steps to reproduce the behavior

No response

Expected behavior

No response

Log files

No response

PICS file

No response

Screenshots

No response

Environment

TH version: matter-th-fall2023

Additional Information

No response

rquidute commented 8 months ago

Hi @manjunath-grl Can you help on this?

cecille commented 8 months ago

This cannot be done manually. These tests are slated to be automated in python by the CSA staff. Are you currently writing automation for these?

Yinxq commented 8 months ago

Hi @cecille. I am using Test Harness to test our chip to make it pass certification testing. According to section 2.1.5 of matter spec1.2, Node Operational Credentials cluster is mandatory to test. Feeding the PICS of this cluster into Test Harness shows that the testcases TC-OPCREDS-3.1, TC-OPCREDS-3.4 and TC-OPCREDS-3.5 need to be tested manually, and generating the NOC chain is in the test steps.

If this can't be done manually as you say, could I pass the official certification testing for the Node Operational Credentials cluster?

Also, where should I check which testcases are mandatory to test, thanks a lot if you can tell me!

cecille commented 8 months ago

I realize this, but 3.1 at the very least is definitely NOT being run currently. @raju-apple - can you comment on where this might be documented? I assure you that this cannot be done manually. The aim is to have these test cases automated for TE2.of 1.3.