Skip to content

test(mobile): use explicit expected values in isServer consistency test#355

Open
guesung wants to merge 2 commits intotoss:mainfrom
guesung:test/isserver-explicit-assertions
Open

test(mobile): use explicit expected values in isServer consistency test#355
guesung wants to merge 2 commits intotoss:mainfrom
guesung:test/isserver-explicit-assertions

Conversation

@guesung
Copy link
Copy Markdown
Contributor

@guesung guesung commented Apr 1, 2026

Summary

  • Replace relative assertions (toBe(secondCall)) with explicit expected values (toBe(false)) in isServer client-side consistency test
  • Aligns with the pattern used in isServer.ssr.test.ts and getSafeAreaInset.ssr.test.ts

Test plan

  • yarn test passes

Copilot AI review requested due to automatic review settings April 1, 2026 00:48
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the isServer client-side consistency test to assert explicit expected values instead of comparing results across calls, aligning the test style with other SSR-related tests in the repo.

Changes:

  • Replaced relative equality assertions (toBe(secondCall)) with explicit boolean expectations (toBe(false)) for isServer() repeated calls.

Copy link
Copy Markdown
Collaborator

@kimyouknow kimyouknow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants