feat(checks): show scenario and check error details in suite report

[kevinmessiaen]

• Add failures_and_errors on ScenarioResult and TestCaseResult
• Refactor suite dots to use STATUS_MAPPING symbols
• Render failures in Panels with FAILURES/SUMMARY sections and nested check output
• Align CheckResult rich output with tab-separated details for non-pass states

New report:

Old report:

[gemini-code-assist]

Summary of Changes

Hello, 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 significantly improves the clarity and detail of test suite reports, particularly when tests fail or encounter errors. By introducing new properties to aggregate failures and restructuring the console output with rich.panel.Panel and distinct status symbols, the changes make it much easier for users to quickly identify, understand, and debug issues within their test runs. The overall impact is a more user-friendly and informative reporting experience.

Highlights

• Enhanced Failure Reporting: The suite report now provides detailed error and failure information for scenarios and checks, presented in structured panels and a comprehensive summary.
• New Failure Accessors: Added failures_and_errors properties to ScenarioResult and TestCaseResult classes, allowing easier programmatic access to failed or errored sub-results.
• Refactored Suite Dots: The visual 'dots' representation in the suite report has been refactored to use dedicated symbols ('E' for error, 'F' for fail, '.' for pass, 's' for skip) for clearer status indication.
• Improved Check Result Output: Individual CheckResult console output now includes the error message directly, tab-separated, for non-passing states.

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

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 significantly improves the suite report by providing more detailed information about failures and errors. The addition of failures_and_errors properties on result objects is a good design choice. The new report structure with "FAILURES" and "SUMMARY" sections, using rich.Panel for details, greatly enhances readability. The refactoring to use symbols from STATUS_MAPPING for the dots view is a nice cleanup. I have one minor suggestion regarding the indentation in the summary section to improve consistency.

[henchaves]

could move it outside the method, making possible to call suite_result.failures_and_errors

[henchaves]

LGTM!