🧪 Add tests for ProfileCard component

[is0692vs]

🎯 What: The testing gap addressed for ProfileCard.tsx. Added a test file src/components/__tests__/ProfileCard.test.tsx to cover the presentational ProfileCard component, addressing the missing coverage for its various rendering states based on UserProfile props.

📊 Coverage:

• Basic profile rendering (avatar, login, name, stats, join date).
• Fallback behavior when name is null (defaults to login).
• Rendering of optional fields (bio, company, location, blog).
• Behavior when optional fields are null (they do not render).
• Organizations list rendering.
• Pinned repositories rendering.
• Edge cases for pinned repositories lacking descriptions or primary languages.

✨ Result:

• Increased test coverage for src/components/ProfileCard.tsx.
• Improved reliability of the UI component by verifying all display conditional branches and fallbacks.
• Ensures future refactors to ProfileCard can be done confidently without inadvertently breaking its layout or fallback logic.

---

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

Greptile Summary

ProfileCard.tsx の表示ロジックを網羅したテストファイル ProfileCard.test.tsx を追加しています。基本情報のレンダリング、名前 null 時のフォールバック、オプションフィールドの表示・非表示、Organizations、Pinned Repos など主要な分岐はほぼカバーされており、コンポーネントの振る舞いを適切に検証しています。

Confidence Score: 5/5

テスト追加のみの PR であり、プロダクションコードへの変更はないため安全にマージ可能です。

全ての指摘が P2（スタイル・品質改善）であり、機能的なバグや正確性の問題はありません。コンポーネントの主要な表示分岐はほぼ網羅されており、テストロジック自体は正しく動作します。

特に注意が必要なファイルはありません。

Important Files Changed

Filename	Overview
src/components/tests/ProfileCard.test.tsx	ProfileCard の主要な表示分岐を網羅したテストを追加。ロケール依存の数値フォーマット検証やフォールバック名のアサーション弱さなど P2 の改善点がある。

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    PC[ProfileCard コンポーネント] --> A[基本情報のレンダリング\nname / login / stats / joinDate]
    PC --> B[name が null のとき\nlogin にフォールバック]
    PC --> C[オプションフィールド\nbio / company / location / blog]
    PC --> D[オプションフィールドが null\n非表示を確認]
    PC --> E[Organizations\nリスト表示]
    PC --> F[Pinned Repositories\nリスト表示]
    F --> G[description / language あり]
    F --> H[description / language なし\nエッジケース]

    style A fill:#4ade80,stroke:#16a34a
    style B fill:#facc15,stroke:#ca8a04
    style C fill:#4ade80,stroke:#16a34a
    style D fill:#4ade80,stroke:#16a34a
    style E fill:#4ade80,stroke:#16a34a
    style G fill:#4ade80,stroke:#16a34a
    style H fill:#4ade80,stroke:#16a34a

Loading

Prompt To Fix All With AI

This is a comment left during a code review.
Path: src/components/__tests__/ProfileCard.test.tsx
Line: 46-48

Comment:
**`toLocaleString()` のロケール依存によるテスト不安定性**

コンポーネントは `profile.followers.toLocaleString()` をロケール引数なしで呼び出しており、テストも `"1,000"` という形式を期待しています。ただし、CI 環境やローカル環境のデフォルトロケールが `en-US` 以外の場合（例: `de-DE` だと `"1.000"`）、テストが失敗する可能性があります。`following` (50) と `public_repos` (100) の検証はロケールに依存しないため安全ですが、`"1,000"` の検証は脆弱です。

コンポーネント側でロケールを固定するか、テスト側で `toLocaleString()` の期待値を動的に生成する方が堅牢です。

```suggestion
    expect(screen.getByText((1000).toLocaleString())).toBeInTheDocument();
```

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: src/components/__tests__/ProfileCard.test.tsx
Line: 57-61

Comment:
**フォールバック名のアサーションが弱い**

`expect(headings.length).toBeGreaterThan(0)` は「"octocat" というテキストを持つ要素が 1 つ以上存在する」ことしか保証しません。`name: null` のときに h2 が `login` を表示するというフォールバックロジックを明示的に検証できていません。`getByRole` を使うと意図がより明確になります。

```suggestion
    expect(screen.getByRole("heading", { level: 2, name: "octocat" })).toBeInTheDocument();
```

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: src/components/__tests__/ProfileCard.test.tsx
Line: 90-92

Comment:
**`getByText` 後の `toBeInTheDocument()` が冗長**

`screen.getByText(...)` は対象要素が見つからない場合に例外をスローするため、直後の `.toBeInTheDocument()` は実質的に何も検証していません。同じパターンがこのファイルで複数回使われています（例: 96〜97行目）。

ポジティブアサーションには `getByText` だけで十分です。要素の不在確認には `queryByText(...).not.toBeInTheDocument()` を使います。

```suggestion
    screen.getByText("Organizations");
    screen.getByText("github");
```

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "🧪 Add tests for ProfileCard component" | Re-trigger Greptile}

Greptile also left 3 inline comments on this PR.

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

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
github-user-summary	Ready	Preview, Comment	Apr 17, 2026 8:10am

[coderabbitai]

Warning

Rate limit exceeded

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

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 51 minutes and 15 seconds.

⌛ 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: 6da9b901-d266-401f-becf-4bd375683fda

📥 Commits

Reviewing files that changed from the base of the PR and between 3be157d and c2061c7.

📒 Files selected for processing (1)

• src/components/__tests__/ProfileCard.test.tsx

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch jules-7299788118637011558-f8a061ee

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[gemini-code-assist]

Code Review

This pull request introduces a comprehensive test suite for the ProfileCard component, covering basic profile information, optional fields, and the rendering of organizations and pinned repositories. The review feedback suggests improving test robustness by replacing hardcoded, locale-dependent number strings with dynamic formatting and utilizing more precise queries, such as getByRole, to verify fallback behavior for user names.