Add unit tests for DefaultHomeRemoteDataSource

[MihaiCristianCondrea]

Summary

• add DefaultHomeRemoteDataSource unit tests that capture the Volley request
• verify successful responses filter out internal package names and deliver valid items
• assert that network errors surface as empty lists for the callback

Testing

• ./gradlew test (fails: Android SDK not configured in environment)

---

https://chatgpt.com/codex/tasks/task_e_68c8479caa38832d8f8b6a14c06c0fe2

[chatgpt-codex-connector]

Codex Review: Here are some suggestions.

Reply with @codex fix comments to fix any unresolved comments.

About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you open a pull request for review, mark a draft as ready, or comment "@codex review". If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex fix this CI failure" or "@codex address that feedback".

[chatgpt-codex-connector]

[P1] Avoid instantiating Android Handler in local unit test

The new unit tests run from app/src/test, but DefaultHomeRemoteDataSource’s constructor immediately calls new Handler(Looper.getMainLooper()). On the plain JVM the Android stubs throw RuntimeException("Stub!") when either Handler or Looper is invoked, so the test will crash before any assertions run unless Robolectric or an instrumentation runner is used. Consider moving the test under androidTest or adding Robolectric/shadow configuration so the handler can be created.

Useful? React with 👍 / 👎.