Added the detailed instruction for validating this test on reference platform

[KishokG]

Added the detailed notes for validating this test on reference platform on how to generate the QR code payloads manually.

[gemini-code-assist]

Summary of Changes

Hello @KishokG, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the tcdd14 test case by providing more comprehensive guidance for validating concatenated QR code onboarding payloads. It clarifies the test procedure for scanning QR codes and includes explicit instructions for generating QR code payloads manually, which is crucial for testing on reference platforms that do not natively support multiple QR codes.

Highlights

• Test Step Description Update: The description for the first test step in tcdd14.py was updated to clarify scanning a larger QR code for commissioning multiple DUTs.
• Manual QR Code Payload Generation Instructions: Detailed instructions were added to the QR code payload input prompt, guiding users on how to manually generate individual QR codes using chip-tool for validation on reference platforms.
• Copyright Year Update: The copyright year range in tcdd14.py was extended from 2023 to 2023-2026.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• onboarding_payload_test_suite/tcdd14/tcdd14.py
  • Updated the copyright year range to 2023-2026.
  • Revised the description of the initial test step for scanning QR codes.
  • Expanded the QR code payload input prompt with detailed instructions for manual generation using chip-tool.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds detailed instructions for validating tests on a reference platform. The changes are a good step towards improving the test's usability. I have two suggestions to further enhance clarity. First, the test step description could be more precise about what is being verified. Second, the example in the user prompt could be improved to show a concatenated QR code payload, which would reduce potential confusion for the user.

[cjandhyala]

@KishokG Do you think we need this PR ? DUTs will have concatenated QR codes, we don't need to mention on how to generate the QR codes.