groups.json: add missing test

[mirostauder]

add missing test to groups.json
omitted in PR5291

Summary by CodeRabbit

• Tests
  • Updated test group configuration to support additional test coverage.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[gemini-code-assist]

Summary of Changes

Hello @mirostauder, 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 a specific test case, reg_test_5233_set_warning-t, into the project's test group configuration. The primary goal is to correct an oversight from a prior pull request, thereby enhancing the robustness of the test suite and ensuring that this particular test is executed as intended.

Highlights

• Test Case Addition: A previously omitted test case, reg_test_5233_set_warning-t, has been added to the groups.json configuration file.
• Correction of Prior Oversight: This change rectifies an omission from a previous pull request, PR5291, ensuring comprehensive test coverage.

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

[coderabbitai]

📝 Walkthrough

Walkthrough

A new test group entry reg_test_5233_set_warning-t was added to the test groups mapping configuration. This registers a new test group identifier for the test suite without modifying any existing entries or control flow.

Changes

Cohort / File(s)	Summary
Test Configuration test/tap/groups/groups.json	Added new test group mapping entry reg_test_5233_set_warning-t to test groups registry

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A test group hops into view,
reg_test_5233_set_warning-t shiny and new!
In JSON it nests with care,
More coverage, more tests everywhere! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: adding a missing test entry to groups.json, which matches the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a8e759c and b91dac0.

📒 Files selected for processing (1)

• test/tap/groups/groups.json

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)

• GitHub Check: CI-builds / builds (debian12,-dbg)
• GitHub Check: CI-builds / builds (ubuntu22,-tap-asan)
• GitHub Check: CI-builds / builds (ubuntu22,-tap)
• GitHub Check: run / trigger

🔇 Additional comments (1)

test/tap/groups/groups.json (1)

86-87: LGTM! New test group entry correctly references an existing test.

The entry for reg_test_5233_set_warning-t properly uses the standard g1 test group configurations and is correctly placed at the end of the g1 section. JSON syntax is valid. The corresponding test file exists at test/tap/tests/reg_test_5233_set_warning-t.cpp.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[gemini-code-assist]

Code Review

This pull request adds a missing test case to the groups.json file. The change is functionally correct and adds the test to the appropriate group. However, there is a minor formatting issue where a blank line with unnecessary whitespace is introduced. I've provided a suggestion to clean this up for consistency.

[gemini-code-assist]

This blank line contains unnecessary whitespace. For consistency with the rest of the file, where blank lines are empty, please remove the spaces.