project-chip / project-chip/certification-tool

[Bug] Need to copy commissioner_dut folder in Test Harness

Open Beginner friendly
#954 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Bug Needs Triage
Dominant language
Shell
Stars
82
Forks
47
Avg merge
1d 15h
Merged PRs (30d)
17

Description

Describe the bug

In Test Case DA-1.4, DA-1.8, These test cases are Vertification Steps Document.

The following is included in the Test Step of the Test Plan Verification document:
./chip-all-clusters-app --trace_decode 1 --dac_provider $CHIP_ROOT/credentials/development/commissioner_dut/invalid_paa/test_case_vector.json --product-id 32768
It indicates the use of a JSON file inside the commissioner_dut folder. However, this file is missing from the Test Harness, causing an issue where it has to be copied externally.

Therefore, we also need to copy the files in the commissioner_dut folder, as shown in the Dockerfile below.
https://github.com/project-chip/connectedhomeip/blob/c736a6be54bb8dd2cedb49820dce90ebe52065a6/integrations/docker/images/chip-cert-bins/Dockerfile#L433

Steps to reproduce the behavior

No response

Expected behavior

No response

Log files

No response

PICS file

No response

Screenshots

No response

Environment

No response

Additional Information

No response

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 reviewing the test harness setup and the referenced integrations/docker/images/chip-cert-bins/Dockerfile section around line 433. Trace how test assets are copied, then ensure the commissioner_dut files, including test_case_vector.json, are available to the DA-1.4 and DA-1.8 verification steps without external copying.

Written by the indexing model from the issue text.

Assessment

Tech stack
dockerfile, shell
Domain
testing
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.