Skip to content

chore: run unit tests on CI#52

Draft
janicduplessis wants to merge 2 commits into
mainfrom
@janic/ci-run-tests
Draft

chore: run unit tests on CI#52
janicduplessis wants to merge 2 commits into
mainfrom
@janic/ci-run-tests

Conversation

@janicduplessis

Copy link
Copy Markdown
Collaborator

Summary

CI had lint and build jobs but never ran the Jest suite, so the prop-resolution tests in src/__tests__/ (~1000 lines) gated nothing — a regression in the JS layer would ship silently. This adds a test job mirroring the existing lint job.

Test Plan

yarn test passes locally (3 suites, 82 tests). This PR's own CI run demonstrates the new job working.

… collision

The app project generated by expo prebuild was named Ease, the same as
the development pod. CocoaPods recreates a user scheme for the pod on
every pod install, and xcodebuild resolved -scheme Ease to the pod's
scheme, so expo run:ios built only the static library and then failed
to find the app binary. Naming the app EaseExample keeps the two
schemes distinct.
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.

1 participant