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

Test scripts use different ways to define the default Test Event Trigger Key

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

@akrithika27 is already working on this.

Since Mar 8, 2024.

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

Description

In the current version of the Test Scripts there are two different ways to define the default Test Event Trigger Key:

  1. 0x000102030405060708090a0b0c0d0e0f
    This is used by the function send_test_event_triggers() in src/python_testing/matter_testing_support.py which is always called without the key parameter. Thus the default key 0x000102030405060708090a0b0c0d0e0f gets used or the value of the global parameter enableKey if it exists

  2. 0x00112233445566778899aabbccddeeff
    This is hard-coded as a default in various YAML scripts like for DGGEN-2.1, DD-3.2, DD-3.6, DD-3.8, etc.

IMHO we should at least unify the hard-coded default keys to one value for all scripts to avoid confusion on the tester side.

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.