mattermost-mobile/detox

How to Run Detox Tests

This guide will help you set up and run Detox tests for your project.

Install Dependencies

First, navigate to the root directory of your project and install the necessary dependencies by running:

npm install

navigate to the detox folder and run npm install

Android

Build Detox Android App

To build the Detox Android app, navigate to the detox folder and run:

npm run e2e:android-inject-settings

npm run e2e:android-build

The debug apk will be built and available at android/app/build/outputs/apk/debug/app-debug.apk

Run Detox Android Tests

Create emulator

./create_android_emulator.sh SDK_VERSION AVD_NAME

# example ./create_android_emulator.sh 34 pixel_5a_avd
# example ./create_android_emulator.sh 34 pixel_5a_avd --headless
# If we want to see the emulator logs. Run it in debug mode example ./create_android_emulator.sh 34 pixel_5a_avd --debug

To execute the Detox tests on Android, navigate to the detox folder and run:

npm run e2e:android-test

# To run a particular tests

npm run e2e:android-test <path to test file>

iOS

Build iOS Simulator

To build the iOS simulator for Detox, navigate to the detox folder and run:

npm run e2e:ios-build

This will build the Simulor .zip file at the root folder.

Create a folder named mobile-artifacts at the project root. Unzip the zip file and move the mattermost app under mobile-artifacts.

# From project root
mkdir mobile-artifacts

Run iOS Tests

To execute the Detox tests on iOS, navigate to the detox folder and run:

npm run e2e:ios-test

# To run a particular tests

npm run e2e:android-test path to test file.

TIP : For iOS, you can download the simulator from ~Mobile: Test build or ~Release: Mobile Apps channel in the community.

Results

The Local Runs generate artifacts under detox/artifacts/ios-debug-** or detox/artifacts/android-debug-**. You can see the html report, failure screenshot under that folder.

Playbooks Tests (AI-Powered Testing)

The Playbooks tests leverage AI-powered testing through the Wix Pilot framework, enabling natural language test creation and execution.

How It Works

The Playbooks tests utilize the pilot library, which connects to Anthropic Claude via the ClaudePromptHandler. This innovative approach allows you to:

• Write tests using natural language prompts
• Automatically translate prompts into executable test steps
• Maintain tests more intuitively through conversational interfaces
• Handle complex scenarios with AI-generated test logic

The system integrates seamlessly with your existing Detox test infrastructure while adding AI capabilities.

Best Practices

For reliable and effective Playbooks tests, follow these guidelines from the Pilot Best Practices Guide:

1. Prompt Clarity:

   • Write clear, concise prompts
   • Use specific action-oriented language
   • Avoid ambiguous phrasing

2. Test Design:

   • Keep prompts focused on single scenarios
   • Use deterministic language to prevent flaky tests
   • Structure complex tests as sequences of simple prompts

3. Maintenance:

   • Review AI-generated test steps before committing
   • Version control both prompts and generated code
   • Monitor test stability regularly

4. Integration:

   • Combine AI tests with traditional assertions
   • Use AI for complex scenarios, traditional methods for simple verifications
   • Document which tests are AI-generated

Getting Started

To run Playbooks tests:

1. Set up your environment:

   export ANTHROPIC_API_KEY='your-api-key-here'
   

2. Run tests normally:

   • The system will automatically initialize the ClaudePromptHandler when the API key is detected
   • No additional configuration is required beyond the API key

3. Execution examples:

   # Run all Playbooks tests
   npm run e2e:android-test tests/playbooks/
   
   # Run a specific Playbook test
   npm run e2e:ios-test tests/playbooks/playbooks_basic.e2e.ts
   

Technical Notes

• The Pilot framework handles the translation between natural language prompts and executable code
• Tests are cached locally after generation for faster subsequent runs
• All AI interactions are logged in the test artifacts for debugging
• The system falls back to traditional testing methods if the API key isn't available

For complete documentation, see:

• Wix Pilot Technical Overview
• Pilot Best Practices Guide