🧪 Add tests for Theme appearance preferences

[SayanthRock]

User description

🎯 What: Added comprehensive test coverage for AppearancePreferences and AppearanceSettingsSaver, which were previously missing tests. In doing so, I also updated AppearancePreferences slightly to allow overriding preferences for testability, given the limitations of EncryptedSharedPreferences within Robolectric testing environments.

📊 Coverage:

• Loading default settings when no preferences exist.
• Saving custom settings and ensuring they are correctly restored.
• The AppearanceSettingsSaver logic for saving state.
• Gracefully handling and falling back to default when loading invalid enums.

✨ Result: Enhanced test coverage that guarantees our user's appearance preferences (like light/dark mode, dynamic color, etc.) are accurately saved, loaded, and protected against parsing crashes.

---

PR created automatically by Jules for task 168628106807272731 started by @SayanthRock

---

CodeAnt-AI Description

Add coverage and safe fallback behavior for appearance preferences

What Changed

• Added tests covering default appearance settings, saving and restoring custom settings, and Compose state restoration
• Verified invalid theme values fall back to the system theme instead of causing a failure
• Made appearance preferences replaceable for reliable testing without changing encrypted storage for users

Impact

✅ Safer theme preference loading
✅ Reliable restoration of light, dark, and system themes
✅ Fewer crashes from invalid saved settings

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

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

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[codeant-ai]

🤖 CodeAnt AI — Review Status

Status	Commit	Started (UTC)	Finished (UTC)
✅ Reviewed your PR	0f676eb	Aug 04, 2026 · 12:43	12:45

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[codeant-ai]

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[coderabbitai]

Warning

Review limit reached

@SayanthRock, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 49 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 081f8a11-3145-4db5-b030-24e83dd5fb89

📥 Commits

Reviewing files that changed from the base of the PR and between c15d063 and 0f676eb.

📒 Files selected for processing (4)

• .jules/testing.md
• app/src/main/java/com/rockmusic/app/presentation/theme/AppearancePreferences.kt
• app/src/test/java/com/rockmusic/app/presentation/theme/AppearancePreferencesTest.kt
• pr_description.md

---

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

[ai-coding-guardrails]

I've got 1 comment for you to consider

Risk: 🟢 Low

Risk analysis

The primary risk introduced by this diff is in security_impact, due to exposing the preferences property as public open, which weakens encapsulation and could allow direct access to sensitive preference data. The test_coverage score is high because the PR adds substantial unit tests for preference loading, saving, and error handling. blast_radius is low because the changes are confined to a single component, and operational_risk is minimal as no infrastructure or deployment changes are involved.

Did you know Zenable also supports GitLab SaaS and self-managed?