[Bug] [Version: v2.15.1-beta1+summer2026 Sha: f49b828] Few Python script Test cases are not Listed in the TH UI, But available inside the Docker.

[Ashwinigrl]

Describe the bug

The following Test cases are missing in the TH Version: v2.15.1-beta1+summer2026 Sha: f49b828, But these are available inside the Docker. Hence these test cases should be displayed in 1.6.1MSVE TH.

Test case list:

• TC-CNET-4.11
• TC-DA-1.7
• TC-OPCREDS-3.8
• TC-TSTAT-2.2

Steps to reproduce the behavior

No response

Expected behavior

All the above Test cases should be displayed in TH UI(Version: v2.15.1-beta1+summer2026 Sha: f49b828).

Log files

No response

PICS file

No response

Screenshots

TH UI:

Python inside Docker:

Environment

TH Version: v2.15.1-beta1+summer2026
Sha: f49b828

Additional Information

No response

[Ashwinigrl]

@rquidute and @antonio-amjr Could you please take a look at this issue?

[rquidute]

Hi @Ashwinigrl , I'm sharing my analysis.
It appears to be a script-level issue in the SDK Python test scripts.

• TC-DA-1.7: 'TC_DA_1_7' object has no attribute 'allow_sdk_dac' — steps_TC_DA_1_7() reads self.allow_sdk_dac, which is only set in setup_class().
• TC-OPCREDS-3.8 (TC_OPCREDS_VidVerify): 'TC_OPCREDS_VidVerify' object has no attribute 'event_loop' — its steps_* runs the decorated test body to collect steps, and the decorator calls self.event_loop.run_until_complete(...).
• TC-TSTAT-2.2: 'NoneType' object has no attribute 'pics' — pics_TC_TSTAT_2_2() calls self.check_pics(...), which reads self.matter_test_config, not populated outside a real run.

TC_CNET_4_11 is a YAML script and it's located inside SDK YAML Test / FirstChipToolSuite

[rquidute]

I transferred this issue to scripts repo since it's seems to be script issues

[Ashwinigrl]

@rquidute Could you please confirm which TH image you are using to see the TC-CNET-4.11 test case—1.7 TE1 or 1.6.1 MVE TH?

We can see TC-CNET-4.11 in the 1.7 TE1 TH, but it is not available in the 1.6.1 MVE TH.

However TC-CNET-4.11 Test case has been migrated from yaml to python after 1.7 TE1 TH build. Currently TC-CNET-4.11 Test case is available in the 1.6.1 MVE branch.

1.7 TE1 TH:

1.6.1 MVE TH:

[Ashwinigrl]

Hi @Ashwinigrl , I'm sharing my analysis. It appears to be a script-level issue in the SDK Python test scripts.

• TC-DA-1.7: 'TC_DA_1_7' object has no attribute 'allow_sdk_dac' — steps_TC_DA_1_7() reads self.allow_sdk_dac, which is only set in setup_class().
• TC-OPCREDS-3.8 (TC_OPCREDS_VidVerify): 'TC_OPCREDS_VidVerify' object has no attribute 'event_loop' — its steps_* runs the decorated test body to collect steps, and the decorator calls self.event_loop.run_until_complete(...).
• TC-TSTAT-2.2: 'NoneType' object has no attribute 'pics' — pics_TC_TSTAT_2_2() calls self.check_pics(...), which reads self.matter_test_config, not populated outside a real run.

@raul-marquez-csa Could you please take a look at these test cases script issues? Thanks!

[rquidute]

Hi @Ashwinigrl Correcting my earlier comment — TC-CNET-4.11 is not a YAML/version-lag issue after all. I traced the actual error and found a genuine script bug, same category as DA-1.7/OPCREDS-3.8/TSTAT-2.2.

Root cause: TC_CNET_4_11.py imports default_matter_test_main, has_feature, and run_if_endpoint_matches from the wrong module:
from matter.testing.matter_testing import MatterBaseTest, TestStep, default_matter_test_main, has_feature, run_if_endpoint_matches

Suggestion of fix:
Replace this line

-from matter.testing.matter_testing import MatterBaseTest, TestStep, default_matter_test_main, has_feature, run_if_endpoint_matches

by this

+from matter.testing.decorators import has_feature, run_if_endpoint_matches
+from matter.testing.matter_testing import MatterBaseTest
+from matter.testing.runner import TestStep, default_matter_test_main