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

TC-I-2.3: Test failure

Open
#577 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Please follow the below template to file issues/concerns/feature enhancement against Test Scripts:

Summary Title:

TC-I-2.3 test failure

Description:

Have we OVER Q'd? I'm only getting two reports.

Steps to reproduce:

EP=1 FILE=TC_I_2_4 TEST=TC_I_2_4; python3 python_testing/scripts/sdk/${FILE}.py --discriminator 3840 --passcode 20202021 --storage-path admin_storage.json --endpoint ${EP} --bool-arg allow_provisional:true --trace-to json:log --tests test_${TEST} --timeout 10000 --paa-trust-store-path /paa_roots 2>&1 | tee logs/DuttyMcDutface_${TEST}_EP${EP}.log

Logs:

DUT
tc_i_2_3_failure.txt

TH

DuttyMcDutface_TC_I_2_4_EP1.log

Additional Info:

Please include any other additional or relevant information here. Example: Spec version, PICS version, Test plan version, PICS XML files used for testing PICS, Configuration of the project, related issues,  etc.

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.

Research direction

Start by reproducing the supplied command for python_testing/scripts/sdk/TC_I_2_4.py with test_TC_I_2_4, then inspect tc_i_2_3_failure.txt and DuttyMcDuface_TC_I_2_4_EP1.log. Determine why only two reports are produced and document the failure's expected result and a reproducible verification.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.