The 'Why'
Why
The repository currently includes automated testing for the backend, frontend, and smart contracts, but the React Native mobile application does not have an automated test suite or CI validation.
Without automated tests, regressions in screens, navigation, components, and business logic can go unnoticed until manual testing. Adding a basic testing setup would improve development confidence, make future changes easier to validate, and help maintain consistent behavior across the project's different platforms.
Feature Category
Backend/Analytics
Proposed Logic/UI
Proposed Implementation
- Add Jest as the default test runner for the React Native application.
- Integrate React Native Testing Library for component and screen testing.
- Add a
test script (and optionally test:watch or test:ci) to mobile/package.json.
- Include a small set of initial tests for core screens and reusable components.
- Extend the GitHub Actions CI workflow to install mobile dependencies and execute the mobile test suite on every pull request.
This would bring the mobile application in line with the automated validation already present for the backend, frontend, and smart contract components.
The 'Why'
Why
The repository currently includes automated testing for the backend, frontend, and smart contracts, but the React Native mobile application does not have an automated test suite or CI validation.
Without automated tests, regressions in screens, navigation, components, and business logic can go unnoticed until manual testing. Adding a basic testing setup would improve development confidence, make future changes easier to validate, and help maintain consistent behavior across the project's different platforms.
Feature Category
Backend/Analytics
Proposed Logic/UI
Proposed Implementation
testscript (and optionallytest:watchortest:ci) tomobile/package.json.This would bring the mobile application in line with the automated validation already present for the backend, frontend, and smart contract components.