Implement CLI Support for Push AV Tests

[rquidute]

What changed

This PR implements CLI support for Push AV (Push Audio/Video) Stream Transport tests via the CLI.

How It Works

The CLI presents Push AV verification prompts using the same interface as the Test Harness browser UI:

1. When a Push AV test runs, the CLI starts a local HTTP server
2. The CLI displays a URL to the user (e.g., http://192.168.1.50:8999)
3. User opens the URL in their browser to see the DASH player interface
4. The browser displays the same verification UI as TH web interface
5. User verifies the video stream and clicks PASS/FAIL
6. The CLI forwards the response to complete the test

When executing in TH UI this is how the Push AV prompt is displayed:

Now, the CLI will display a similar prompt like bellow:

The cli execution log shows Push AV tests like bellow:

Related Issue

project-chip/certification-tool#783

Testing

Unit test added and Passing

Run a Push AV test successfully by running this command in CLI: th-cli run-tests -t TC_PAVSTI_1_2 --project-id 2

[gemini-code-assist]

Summary of Changes

Hello @rquidute, 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 integrates Push Audio/Video (AV) Stream Transport tests into the CLI workflow, providing a robust mechanism for users to execute and verify these tests without relying solely on the graphical user interface. It achieves this by introducing a local HTTP server that presents an interactive web-based prompt, allowing users to view and interact with streaming content, and then relaying their responses back to the CLI. This significantly enhances the automation and flexibility of Push AV testing.

Highlights

• CLI Support for Push AV Tests: This pull request introduces comprehensive command-line interface (CLI) support for Push Audio/Video (AV) Stream Transport tests, enabling users to execute and verify these tests directly from the terminal.
• Interactive Web-Based Prompt: A new interactive web-based prompt has been implemented for Push AV tests, mirroring the user experience of the existing UI. This prompt allows users to view available streams, play video content, and provide pass/fail responses.
• HTTP Server Enhancements for Streaming: The CameraHTTPServer has been significantly enhanced to support Push AV streaming. This includes new endpoints for fetching stream lists (/api/streams), proxying stream data (/api/stream_proxy), and a simplified base64-encoded URL proxy (/proxy/). The server now dynamically rewrites DASH MPD manifests to ensure proper playback through the local proxy.
• Dedicated HTML Template for Push AV Verification: A new HTML template, push_av_stream_verification.html, has been added. This template provides the user interface for interacting with Push AV streams, including stream selection, video playback via DASH.js, display of stream contents, and conformance status.
• Expanded Prompt Manager Functionality: The prompt_manager module has been updated to handle PushAVStreamVerificationRequest and ImageVerificationPromptRequest types, routing them to appropriate handlers and integrating with the new HTTP server for interactive user input.
• New Unit Tests: New unit tests have been added for camera_http_server and prompt_manager to ensure the reliability and correctness of the newly introduced Push AV CLI functionality and HTTP server enhancements.

🧠 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.

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 successfully implements CLI support for Push AV stream transport tests. It introduces a new web-based verification prompt for Push AV streams, complete with a DASH player and a proxy to handle stream fetching from the Push AV server. The changes are well-structured, with new handlers in prompt_manager.py and camera_http_server.py, a new HTML/JS interface, and corresponding unit tests.

My review focuses on improving security and test quality. I've pointed out the use of disabled SSL verification in httpx clients, which poses a security risk. I've also highlighted several placeholder unit tests that should be implemented to ensure the new validation logic is robust. A minor style issue regarding local imports has also been noted.

Overall, this is a solid implementation of a complex feature. Addressing the feedback will enhance the security and reliability of the new functionality.