🧪 Add missing edge case tests for topic size class calculation

[is0692vs]

🎯 What: The testing gap addressed. Specifically, missing tests for explicit edge cases (count=0, count=maxCount) and boundary condition calculations (like negatives, NaNs, Infinity).
📊 Coverage: Explicitly covers edge case calculations for count=0 and count=maxCount, as well as situations where variables may exceed the expected maximums or evaluate to NaN/Infinity.
✨ Result: Improved test coverage across edge boundaries guarantees confidence when refactoring functions that calculate proportions to string mappings. Tests added: count < 0, count > maxCount, count = 0 (explicit), count = maxCount (explicit), NaN, and Infinity.

---

PR created automatically by Jules for task 16091128659587119313 started by @is0692vs

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
github-user-summary	Ready	Preview, Comment	Mar 21, 2026 4:50am

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[coderabbitai]

Warning

Rate limit exceeded

@is0692vs has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 21 minutes and 41 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 07f75846-19ef-4e25-8b04-af3672f2cc98

📥 Commits

Reviewing files that changed from the base of the PR and between 07766c0 and 014d4da.

📒 Files selected for processing (1)

• src/lib/__tests__/topicUtils.test.ts

📝 Walkthrough

Walkthrough

getTopicSizeClass関数の異常系入力（負数、NaN、無限大など）に対する新しい単体テストを25行追加しました。本番コードの変更はなく、テストケースの拡張のみです。

Changes

コホート / ファイル	概要
テスト拡張 src/lib/__tests__/topicUtils.test.ts	getTopicSizeClassの境界値テストを追加。負のcount、maxCountを超えるcount、count/maxCountのNaN、Infinityなど異常系入力をカバーし、各ケースで期待される戻り値クラス文字列を検証。

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 テストで守る、境界の線
NaNも無限も、ぼくらの仲間
エッジケース退治、コードは安心
パイパイ、テスト完成だぃ！ 🥕✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	タイトルは「🧪 Add missing edge case tests for topic size class calculation」で、プルリクエストの主な変更（トピックサイズクラス計算のエッジケーステスト追加）を明確に要約しており、変更セットと完全に関連している。
Description check	✅ Passed	説明は変更セット内のテスト追加に関連しており、具体的なカバレッジ内容（count=0、count=maxCount、負の値、NaN、Infinity）を記載しており、変更と関連している。
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.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch test/topic-size-class-16091128659587119313

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[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 test suite's robustness by introducing comprehensive edge case testing for the getTopicSizeClass utility function. The additions cover a wide range of boundary conditions and invalid inputs, ensuring the function's stability and predictability, which is crucial for future refactoring and maintenance.

Highlights

• Test Coverage Expansion: Expanded test coverage for the getTopicSizeClass function to include critical edge cases and boundary conditions.
• Edge Case Testing: Added specific tests for count being zero, count equaling maxCount, negative count values, count exceeding maxCount, and scenarios involving NaN and Infinity for both count and maxCount.
• Improved Robustness: Ensured that the getTopicSizeClass function behaves as expected under various unusual or extreme input conditions, enhancing its reliability.

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 adds valuable edge case tests for the getTopicSizeClass function, which improves test coverage and confidence in the logic. However, the implementation introduces a significant amount of duplicated test code, with several test blocks being repeated. I've added a comment with a suggestion to refactor the tests by removing the duplicated and redundant code to improve the maintainability and readability of the test suite.

[is0692vs]

レビュー内容を整理します。

全体所感

• gemini-code-assist: This pull request adds valuable edge case tests for the getTopicSizeClass function, which improves test coverage and confidence in the logic. However, the implementation introduces a significant amount of duplicated test code, with several test blocks being repeated.

主な未解決指摘

• [medium] src/lib/tests/topicUtils.test.ts:203 gemini-code-assist: There appears to be a large amount of duplicated test code in this change.

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/lib/__tests__/topicUtils.test.ts`:
- Around line 79-103: Add an inline comment above the NaN/Infinity edge-case
tests in src/lib/__tests__/topicUtils.test.ts explaining that these tests
intentionally pin current implicit behavior of getTopicSizeClass (e.g., NaN
comparisons always false, Infinity behavior) rather than asserting explicitly
handled input validation, so future refactors know these expectations are
deliberate; reference the tested function name getTopicSizeClass and note that
these cases document current behavior rather than enforcing new validation
logic.
- Around line 89-95: The tests expect explicit NaN/Infinity validation: update
getTopicSizeClass to defensively validate its numeric inputs (count and
maxCount) using Number.isNaN and Number.isFinite (or equivalent) and immediately
return "text-xs" when either value is NaN or not finite; keep the existing
sizing logic otherwise. Locate the getTopicSizeClass function and add these
explicit checks at the top before any arithmetic so behavior matches other utils
(e.g., yearInReviewUtils.ts) and the new tests.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: ee376888-e938-48d5-abe6-7ac0d64771a0

📥 Commits

Reviewing files that changed from the base of the PR and between 87d145d and 07766c0.

📒 Files selected for processing (1)

• src/lib/__tests__/topicUtils.test.ts

[is0692vs]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.