Enhancing Mobile Test Automation with WebdriverIO & Appium for a FinTech Investment App

Client Overview: FinTech Leader in Southeast Asia

The Client is a leading FinTech company based in Indonesia, offering a wide range of financial services including stock trading, mutual funds, bonds, cryptocurrencies, and more. With a vision to provide the best mobile and online trading experience in Southeast Asia, the client aims to empower retail investors, particularly the millennial generation, with access to secure and affordable investment options.

Their mission is to modernize the Indonesian capital market and make it one of the most advanced in Southeast Asia. They actively collaborate with stakeholders through educational initiatives such as university seminars and online learning to promote financial literacy.

Business Challenge

As the client scaled its business, they faced challenges in ensuring the reliability of their mobile application across Android and iOS platforms. With only 20% of their test scenarios automated, they were experiencing:

• Inconsistent performance across different devices and environments (staging and production).
• Frequent app crashes due to low test coverage.
• Inefficiencies in managing environment-specific configurations.

• Reporting issues where test reports were being overwritten during each new build.
  To address these issues, The client needed a robust test automation framework that could:

• Increase automation coverage to 100%.

• Ensure daily test execution on multiple environments (staging and production) and platforms (Android and iOS).

• Improve reporting processes and real-time test run notifications.
  **

  Key Challenges

  **

1. **Outdated Automation Framework: **Their current framework was running on outdated versions and needed an upgrade to the latest technologies.
2. Limited Test Automation Coverage: With only 20% test coverage, frequent bugs were making their way into production, impacting user experience.
3. Allure Report Overwriting: In Jenkins, the allure reports were being overwritten with each build, preventing comprehensive tracking of test results.
4. Environment-Specific Challenges: Each environment (staging, production) used different package IDs, complicating the automation process.
5. Login Failures: Initial tests were failing at the login screen, and the root cause of the issue was unclear.
6. Communication Gap: The client needed real-time test result notifications via Slack to streamline the development process.

Want to know how we solved all these challenges?
Click Here!