Fixing the CLI Run Test Logic to handle project config and user config

[antonio-amjr]

Related to: project-chip/certification-tool#816
Related to: project-chip/certification-tool-backend#283

Description

Fixing CLI run_tests() logic to retrieve and use the configuration from the TH project, in case project-id is provided, returning default otherwise.
CLI will print only the project config to the output, unless the config is provided as well in the run-tests() command.

Also, one Unit Test was updated accordingly.

Finally, the CLI config.py file was updated to use a known path for the project as well, to reduce complexity and work for either --editable mode and default th-cli application.

[gemini-code-assist]

Summary of Changes

Hello @antonio-amjr, 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 refines the configuration management for the run_tests CLI command. It introduces a more robust mechanism for fetching test configurations, allowing the CLI to retrieve settings directly from a specified project or use a default set if no project is identified. This ensures that test runs are consistently configured. Additionally, the PR streamlines the internal handling of CLI paths, making the application more resilient to different installation environments and simplifying the process of locating configuration files.

Highlights

• Configuration Retrieval Logic: The run_tests CLI command now intelligently retrieves configuration, prioritizing project-specific settings if a project_id is provided, and falling back to default configurations otherwise. A new helper function, __project_config, encapsulates this logic.
• Configuration Merging: User-supplied configuration files are now merged on top of the retrieved project or default configuration, allowing for easier overrides and a more predictable configuration hierarchy.
• Standardized CLI Paths: The internal configuration handling has been improved by introducing a known_cli_path in the user's home directory, simplifying how the CLI locates configuration files regardless of installation method (e.g., editable vs. standard installs).
• Output Clarity: Updated CLI output messages to clearly distinguish between 'Project Config' and 'CLI Test Run Execution Config', providing better feedback to the user.

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 effectively refactors the CLI's test execution logic to correctly handle project-specific and user-provided configurations. The simplification of configuration file search paths in th_cli/config.py is a good improvement for maintainability. My review includes a high-severity suggestion to add a warning when a specified project ID is not found, preventing silent fallbacks to the default configuration. I've also included a medium-severity suggestion to improve path construction using pathlib best practices.