-
Notifications
You must be signed in to change notification settings - Fork 0
Make local and CI test commands reproducible before bug fixes #9
Copy link
Copy link
Open
Labels
area: buildBuild, packaging, and release configurationBuild, packaging, and release configurationarea: testsAutomated test coverage and test configurationAutomated test coverage and test configurationdocumentationImprovements or additions to documentationImprovements or additions to documentationenhancementNew feature or requestNew feature or requestpriority: criticalMust fix before the next releaseMust fix before the next releasetype: choreMaintenance and internal project workMaintenance and internal project worktype: testingTest infrastructure and coverage workTest infrastructure and coverage work
Milestone
Description
Metadata
Metadata
Assignees
Labels
area: buildBuild, packaging, and release configurationBuild, packaging, and release configurationarea: testsAutomated test coverage and test configurationAutomated test coverage and test configurationdocumentationImprovements or additions to documentationImprovements or additions to documentationenhancementNew feature or requestNew feature or requestpriority: criticalMust fix before the next releaseMust fix before the next releasetype: choreMaintenance and internal project workMaintenance and internal project worktype: testingTest infrastructure and coverage workTest infrastructure and coverage work
Problem
The repository has Jest, lint, typecheck, and CI configured, but the local checkout currently cannot run those commands without installed dependencies. The contributing documentation also still refers to the example app as
example/, while the actual workspace isexample-expo.Before fixing runtime bugs, contributors need a clear and reproducible test path that does not require starting the Expo app or any local server.
Impact
Without a reproducible validation path, bug-fix PRs can change behavior without a reliable signal from tests or CI. The mismatch between docs/config and the actual workspace also makes it harder to know which commands should be trusted.
Code references
package.json#L39-L46: project scripts definetest,typecheck,lint, andprepare..github/workflows/ci.yml#L1-L47: CI already runs lint, typecheck, tests with coverage, library build, and Expo web export..github/actions/setup/action.yml#L1-L23: CI installs dependencies through Yarn.CONTRIBUTING.md#L8-L19: documentation refers toexample/, but the repo usesexample-expo.src/__tests__/index.test.tsx#L1: the only Jest test is a placeholder.Acceptance criteria
example-expoconsistently.