Testing your Mobile App

It's always important to ensure everything is working properly and that's why tests are great. We have unit and e2e tests on this project.
How to inspect the app
We use Reactotron to inspect logs, redux state, redux-sagas, HTTP requests, etc.
Unit tests
We use Jest and Storybook on our tests.
Storybook
Storybook is a tool for developing UI Components and has some plugins to make Jest generate snapshots of them.
​On the root of the project, comment everything leaving only the last import to Storybook left and refresh your project. You'll see some tests like this:
​​
​​
Jest
We use Jest for our unit tests and to generate Storybook snapshots. We have a pre-commit hook enforcing preventing commits that breaks any test.
To check for test issues on your code, run this on your terminal:
yarn test
E2E tests
We use Detox framework to end-to-end test our app and ensure everything is working properly.
​Follow this documentation to learn how to run it.
Code style
We use ESLint to enforce code style and best practices. We have a pre-commit hook enforcing commits to follow our lint rules.
To check for lint issues on your code, run this on your terminal:
yarn lint
Code formatting
We use Prettier to format the code style in our project. We have a pre-commit hook enforcing commits to follow our style guides.
To fix your code formatting issues, run this on your terminal:
yarn prettier
​Check this link to see how to integrate Prettier with your preferred code editor, and run Prettier when saving your file for example.

Analytics & Data Usage

Next - Mobile App

Mobile App White Labelling

Last modified 2mo ago

Export as PDF

Copy link

Edit on GitHub

On this page

How to inspect the app

Unit tests

Storybook

Jest

E2E tests

Code style

Code formatting