Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TE9][TC-DM-2.1] some test steps need returned status UNSUPPORTED_WRITE(0x88) but (UNSUPPORTED_ATTRIBUTE)(0x86) #18248

Closed
wilbur-se opened this issue May 10, 2022 · 4 comments

Comments

@wilbur-se
Copy link
Contributor

Problem

<what's wrong or missing, please include any applicable:

  • expected behavior
  • actual behavior
  • steps to reproduce
  • system configuration
  • screenshots, images, logs, etc.

test step #31, #34, #37, #40, #43, #46, #52, #54, #57 send command "./chip-tool basic write-by-id" but use wrong attribute ID, cause returned status is not expected UNSUPPORTED_WRITE(0x88)

Proposed Solution

<suggested fix, suggested enhancement>

just remove prefix "0x" as decimal attribute ID for this steps, or use right hex attribute ID

@bzbarsky-apple
Copy link
Contributor

Sounds like an issue in the test plan (which one?), not in the SDK.

Please file in https://github.com/CHIP-Specifications/chip-test-plans/ ?

@cjandhyala

@bzbarsky-apple
Copy link
Contributor

In particular, @wilbur-se I don't see any write-by-id in any of the TC-GC steps, so which test is the above referencing?

@wilbur-se wilbur-se changed the title [TE9][TC-GC-2.1] some test steps need returned status UNSUPPORTED_WRITE(0x88) but (UNSUPPORTED_ATTRIBUTE)(0x86) [TE9][TC-DM-2.1] some test steps need returned status UNSUPPORTED_WRITE(0x88) but (UNSUPPORTED_ATTRIBUTE)(0x86) May 24, 2022
@wilbur-se
Copy link
Contributor Author

In particular, @wilbur-se I don't see any write-by-id in any of the TC-GC steps, so which test is the above referencing?

Sorry to write wrong title. It is TC-DM-2.1 not TC-GC2.1

@bzbarsky-apple
Copy link
Contributor

@wilbur-se I filed https://github.com/CHIP-Specifications/chip-test-plans/issues/1342 to track that. Thank you for the corrected testcase title!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants