Comment on page

Testing your Mobile App

Testing is an integral part of mobile app development to ensure the reliability, functionality, and user experience of your Rocket.Chat Mobile app. This guide will walk you through various testing approaches for Rocket.Chat Mobile App. The Rocket.Chat Mobile App has unit tests and e2e tests.

How to inspect the app

Reactotron is used to inspect logs, redux state, redux-sagas, HTTP requests, etc.

Unit tests

Unit tests focus on isolating and testing individual components or functions within your app. They help identify and fix bugs early in the development process and ensure that each part of your app works as intended. For unit tests, we use Jest and Storybook.
Storybook is a tool for developing UI Components with some plugins to make Jest generate snapshots. Navigate to the index.js file on your project's root directory, and keep only the last Storybook import while commenting the remaining part of the code. Then, refresh your project, and you will observe the generation of tests like this:


We use Jest for unit tests and to generate Storybook snapshots. There is a pre-commit hook to prevent commits that breaks any test. To check for test issues on your code, run this command:
yarn test

E2E tests

Detox framework tests our app end-to-end and ensures everything works properly.
To run the test, follow the steps on the e2e GitHub repository.

Code style

ESLint is used to enforce code style and best practices. There is a pre-commit hook enforcing commits to follow our lint rules.
To check for lint issues on your code, run this command:
yarn lint

Code formatting

Prettier is used to format the code style in our project. There is a pre-commit hook enforcing the commits to follow our style guides.
To fix your code formatting issues, run this on your terminal:
yarn prettier-lint
To integrate Prettier with your preferred code editor, see the official documentation.
Last modified 3mo ago
Deprecation for cloud services and apps is now extended to November 20, 2023. Rocket.Chat versions receive support for six months after release.