Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade roboletric and junit versions to be consistent #22395

Merged
merged 7 commits into from
May 9, 2023
Merged

Upgrade roboletric and junit versions to be consistent #22395

merged 7 commits into from
May 9, 2023

Conversation

josephyanks
Copy link
Contributor

Why

The bumping of robolectric to 4.10 means that we no longer need jetifier to translate old support library dependencies.

How

  • Updates robolectric to 4.10 and junit to 4.13.2
  • Updates test dependencies in expo-modules-test-core to their latest versions
  • A minor change needed to be made to the expo-clipboard test because of changes to the way that robolectric handles decoding bitmaps for tests.

Test Plan

Ensured unit tests still pass

Trying to verify end to end tests locally.

Checklist

@expo-bot expo-bot added bot: passed checks ExpoBot has nothing to complain about and removed bot: suggestions ExpoBot has some suggestions labels May 8, 2023
@josephyanks
Copy link
Contributor Author

@Kudo I'm not sure how much I need to worry about these other CI steps failing - it seems like every time they run they fail for a different reason. I've verified that the android unit tests pass locally, and can't get the android instrumentation tests to run. Let me know what needs to be done to get this merged, thanks!

@Kudo
Copy link
Contributor

Kudo commented May 8, 2023

@josephyanks don't worry for that. some failures are intentional. i'm sorry that our ci tests are not friendly for external contributors. i will take care of it, either merge it or let you know if there are any real issues we need to update. thanks!

@josephyanks
Copy link
Contributor Author

@Kudo no worries, just want to make sure I'm being thorough! it should be good to merge once I get the approval then

@wschurman wschurman removed their request for review May 8, 2023 19:25
// Note that on some tests, the pixel value will be -16777216, which is
// 11111111 00000000 00000000 00000000 in binary form. This is also a fully-opaque
// black color, so comparing hex strings is cleaner to capture both acceptable results
// (0 and -16777216).
Copy link
Contributor

Choose a reason for hiding this comment

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

i love this comment. it makes things so clear. thanks for adding this.

Copy link
Contributor

@Kudo Kudo left a comment

Choose a reason for hiding this comment

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

last thing before approving and merging. i think updating bundles inside expo-dev-launcher are unrelated to this pr. i know that this might to resolve ci issues, but don't worry i'll try to fix ci issues in a separated pr. please help to revert the expo-dev-launcher bundles changes. thank you!

@josephyanks
Copy link
Contributor Author

@Kudo Those two bundle updates from expo-dev-launcher should be properly reverted now. Thank you for reviewing!

Copy link
Contributor

@Kudo Kudo left a comment

Choose a reason for hiding this comment

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

everything looks pretty in this pr, i'm going to merge this. thanks for the fantastic pr. 🔥

@Kudo Kudo merged commit d0cf89c into expo:main May 9, 2023
@josephyanks josephyanks deleted the jyanks/update-expo-robolectric-junit branch May 10, 2023 13:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bot: passed checks ExpoBot has nothing to complain about
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants