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

[Ashwinigrl]

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:

• https://github.com/CHIP-Specifications/chip-test-plans/blob/master/src/cluster/scenes.adoc#tc-s-2-2-primary-functionality-with-dut_server

Yaml script References:

• https://github.com/project-chip/connectedhomeip/blob/master/src/app/tests/suites/certification/Test_TC_S_2_2.yaml

[Ashwinigrl]

@lpbeliveau Could you please take a look at this issue?

[Ashwinigrl]

Script PR: project-chip/connectedhomeip#73552