project-chip / project-chip/matter-test-scripts

[TC-S-2.2] Update YAML Script to Handle Backward Compatibility for FabricSceneInfo Deprecated Fields.

Open
#803 2 comments 0 reactions 1 assignee View on GitHub

@lpbeliveau is already working on this.

Since Aug 27, 2026.

Dominant language
Python
Stars
19
Forks
7
Avg merge
3d 17h
Merged PRs (30d)
3

Description

Description:

The TC-S-2.2 (step 3e, 3f) Test Plan has been updated for the 1.7 release, where the SceneValid, CurrentScene, and CurrentGroup fields in the FabricSceneInfo attribute are deprecated.

The Test Plan correctly handles backward compatibility based on the FabricSceneInfo Cluster Revision:

  • Cluster Revision ≥ 2 (1.7 and later):
    • CurrentScene = 0xFF
    • CurrentGroup = 0x00
    • SceneValid = FALSE
  • Cluster Revision < 2 (older releases):
    • CurrentScene = 0x01
    • CurrentGroup = G1
    • SceneValid = TRUE

However, the current YAML script does not include the backward compatibility condition and validates only the current 1.7 behavior.

Issue

When TC-S-2.2 is executed against an older-release DUT, the YAML script expects the 1.7 values for the FabricSceneInfo fields. This results in a value mismatch failure at Step 3f, even though the DUT is behaving correctly according to its applicable specification revision.

Expected Behavior

The script should support both the current 1.7 behavior and backward compatibility with older releases.

Recommendation

Update the TC-S-2.2 YAML script to include the Cluster Revision-based condition so that the test case can correctly validate both 1.7 and older-release DUT behavior.

Steps to reproduce:

Step 3d

Test plan References:

Yaml script References:

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.