Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

TC-CNET-4.24 test case proposal

Aperta
  • Qualcosa non va?
#802 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@r-recchia ci sta già lavorando.

Dal 24/8/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

Suggested changes from posted PR:

  • loosen the check for kNetworkNotFound for devices pre-1.7. Devices before 1.7 should tolerate an incorrect error (any error, but not success) and set a warning (use the record_warning feature to get this printed out at the end of the test). I think 1.7 we should enforce kNetworkNotFound. I think we'll get feedback / complaints during the test event and may need to adjust afterwards, but let's see how this goes as a first test.
  • Eliminate the check for the malformed Network Key - as noted in the meeting, for thread the chances of having a bad network key on an otherwise matching network are slim. The common case would be a not found network. In field devices are definitely failing at this step and we should perhaps fix this in the SDK, but let's not let this block putting the test in
  • fully commission the device at the end of the test so we don't have to wait out the failsafe.
  • We should gate this test on the device reporting itself as having a concurrent connection (SupportsConcurrentConnection in the general commissioning cluster). I'd rather do this check within the test itself since we don't have a strong verification on the PICS, but I think I'll probably end up litigating this in the test event feedback.

Branch with some initial changes - https://github.com/cecille/connectedhomeip/tree/tc_cnet_4_24_proposal

Note that i just commented out the initial check on the xpanid rather than fixing it properly. Branch not properly tested, so use at your own risk, but it should give an illustration of the chnages and a starting point.

Lingua principale
Python
Stelle
20
Fork
7
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di project-chip/matter-test-scripts

Tutte le issue di project-chip/matter-test-scripts

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.