project-chip / project-chip/matter-test-scripts
TC-EEVSE-2.5 fails when run in a batch straight after TC-EEVSE-2.4
Open
Nobody has claimed this yet.
Awaiting Dev Feedback
sve_1.3
- Dominant language
- Python
- Stars
- 19
- Forks
- 7
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 3
Description
Summary Title:
Matter 1.3 SVE [TC-EVSE-2.5] fails when run in a batch straight after TC-EVSE-2.4.
Description:
When using the test harness and selecting multiple tests to run in a batch, then the test cases 2.4 must have left the state of the EVSE such that when running the follow-on TC-EEVSE-2.5.
Specifically it fails on
| TC-EVSE-2.5 | step 3b | {PICS_S}.A0001(SupplyState) | {THread} SupplyState | {valhas} 0x00 (Disabled) |
|---|
This is because the previous test case TC-EEVSE-2.4 has a step
| 5 | {PICS_S}.C02.Rsp(EnableCharging) |
|---|
Either TC-EEVSE-2.4 (and other tests) should explicitly send a Disable command to help clean-up, or the TC-EEVSE-2.5 should explicitly send the disable command.
If you run the 2 test cases separately then it is ok.
Steps to reproduce:
1. In the test harness UI select the 2 test cases TC-EEVSE-2.4 and TC-EEVSE-2.5
2. Start the test run
3. the 1st test case will pass (2.4), the 2nd will fail (2.5) because the DUT initial state isn't as expected.
Logs:
Logs not available -
Additional Info:
N/A
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.