FinCell’s Testing

Hari Mahesh

FinCell is a pre-built mobile banking app solution developed by Baltic Amadeus. It is designed to help financial institutions, such as banks, credit unions, and lending institutions, launch their mobile banking platform quickly and cost-effectively. Instead of developing an app from scratch, financial institutions can customize and rebrand FinCell to match their own brand identity and offer their customers a variety of features, such as:

• Account management
• Payments
• Money transfers
• Bill pay
• Mobile deposits
• Loan applications

FinCell is a good option for any financial institution that wants to launch a mobile banking app quickly and cost-effectively. It is particularly well-suited for small and medium-sized financial institutions that may not have the resources to develop their app.

Testing FinCell

FinCell is a banking application, and they are mainly into mobile applications; testing plays a crucial role here. As mobile devices are prone to jailbreaking or rooting, ensuring the app is safe and there are no related bugs is necessary. Here are the top 10 tools for mobile testing.

So, let’s review the three main testing areas.

Unit Testing

In unit testing, the individual units of the application are tested independently. The unit can be a module, function, or part of the code itself. These units are isolated and tested. The purpose of unit testing is to capture bugs at the code level. Usually, unit testing is considered to be the first level of testing.

As FinCell is a white-label mobile banking app solution, the specific unit testing tools used would depend on the individual financial institution customizing and rebranding it. So, we can consider a few general unit testing tools that can be used for unit testing Android and iOS.

Unit Testing on Android

• JUnit: The foundation of Android unit testing, offering a familiar and straightforward way to test individual code units in isolation. It integrates seamlessly with Android Studio and provides precise test results and reporting.
• Robolectric: Enables unit testing of Android code without relying on a physical device or the Android framework. This speeds up testing significantly and allows testing code that interacts with device-specific features in a controlled environment.
• Mockito: A robust mocking framework that simplifies creating test doubles like mocks and stubs. This lets you isolate units under test from external dependencies, making tests more focused and maintainable.

Unit Testing on iOS

• XCTest: Apple’s built-in unit testing framework is closely integrated with Xcode for a streamlined development experience. It offers a rich set of testing assertions and works well with other Apple testing tools like UI and Performance Testing.
• Quick: A popular alternative to XCTest, known for its more concise and expressive syntax. It encourages writing readable and maintainable tests with features like nested descriptions, shared examples, and property-based testing.
• OCMock: A versatile mocking framework compatible with both Objective-C and Swift projects. It allows the creation of various test doubles, including mocks, stubs, and spies, to isolate units under test effectively and control their behavior in tests.

Integration Testing

Once unit testing is completed, we integrate the units to check how these units perform when integrated as a group. The primary purpose of integration testing is to identify any discrepancies or failures in the interaction between these integrated units. Unlike unit testing, where we focus only on functionality, here we focus on interfaces and interactions between units.

FinCell is a pre-built mobile application where the tools used vary based on the company that buys it. Generally, we can consider the available tools for mobile integration testing.

API Integration Testing

• Postman: With Postman, you can craft various HTTP requests, mimicking real-world interactions with FinCell’s backend APIs. Mocking responses allow controlled testing environments, while data validation ensures the expected information flows smoothly.
• SoapUI: Comprehensive toolset for various web services, including SOAP, REST, and GraphQL, offering functional, security, and performance testing.
• Retrofit (Android) and Alamofire (iOS): HTTP client libraries specifically designed for mobile development facilitate API interaction testing within the app.

Mobile App Integration Testing

• Appium: An open-source framework for automating mobile app testing. While primarily used for UI testing, it can also be used for basic integration testing within the app. However, its suitability depends on the complexity of FinCell’s internal integrations.
• Espresso (Android) and XCTest UI (iOS): Built-in frameworks for UI testing, with limited integration testing capabilities within the app’s user interface.
• Spoon (Android): Records and replays user interactions, potentially helpful for identifying integration issues related to UI behavior.
• EarlGrey (iOS): Offers advanced UI testing features, including integration testing capabilities within the app’s interface.

End-to-End Testing

It is a software testing approach that simulates real-world user scenarios from start to finish. Imagine testing a banking app by logging in, navigating to a specific account, making a transfer, and finally verifying the transaction history. It involves testing all the interconnected components, from the user interface and backend systems to databases and external APIs, ensuring they function seamlessly together to deliver the expected outcome. E2E testing helps catch issues that might emerge in real-world usage, where multiple components interact, offering valuable insights into your application’s overall quality and reliability.

For Fincell, we can use Appium or any other coded automation tools; however, when we automate more test scripts, the code repository gets more complex, so you may need to spend more time debugging rather than creating new scripts.

Also, these tools depend on DOM element locators. When the development technology changes, for example, apps migrating to Flutter, it will be complicated to identify locators. The tools may not have support to recognize the new element locator strategy. So, for E2E testing, it’s always better to choose intelligent automation tools that reduce human intervention and provide stable results.

testRigor

testRigor stands out from most of the E2E automation tools because of its advanced features. It is a generative AI-powered codeless automation tool packed with many features that most automation tools don’t offer. Let’s go through a few of them.

• Mobile testing: Using testRigor, we can execute tests on physical devices and test hybrid apps. Unlike other tools, where we integrate mobile cloud testing platforms for test execution separately, testRigor has built-in integrations with its partners. We just need to create the test script, choose the device and OS version, and execute it; there is no need to go behind setting up the plugins and creating integration codes.
• Test Scripting: While using testRigor, we don’t have to worry about knowledge of programming language. Yes, testRigor helps create test scripts in parsed plain English. So, this advantage helps manual testers immensely. They can create and execute test scripts three times faster than other tools. Also, any stakeholder can add or update test scripts, as they are easy to read and understand.
• Element Locators: Above, we have discussed the drawbacks of using DOM properties of elements. testRigor has a different element locator strategy. We can just mention the text that you see on the screen for the element; testrigor’s AI algorithms will be able to fetch the element and continue automation. So we don’t have to worry about the development/element property changes happening in the application.

These are very few features of testRigor that we mentioned here, but you can read more about it here.

login as customer
click "Accounts"
click "Manage Accounts."
click "Enable International Transactions"
enter stored value "daily limit value" into "Daily Limit"
click "Save"
click "Account Balance" roughly to the left of "Debit Cards"
Check the page contains "Account Balance"

As you can see, no complicated XPath/CSS locator is mentioned, or any complex loops or scripts are required. Using simple English commands, you can execute email, file upload/download, database, 2FA, QR code, Captcha resolution, SMS, phone call, visual, and many more complex tests.

Conclusion

The tools for testing mobile apps are limited as compared to browser testing. But with the available tools, ensuring the app is bug-free and has no security vulnerabilities is mandatory. Choosing the right tool for each test ensures the app is tested correctly and doesn’t consume much time in testing.

We know there are security updates for mobile every month, so there are frequent releases. It is an excellent decision to have an intelligent tool such as testRigor as a support system that can cover a higher test coverage in less time with high quality.

“We spent so much time on maintenance when using Selenium, and we spend nearly zero time with maintenance using testRigor.”

Keith Powe VP Of Engineering - IDT