Testing Banking Applications. Here is a practical example

© 2021 Maveryx srl.
All rights reserved.
Testing Banking Applications.
Here is a practical example

Summary
• Characteristics of Banking Applications
• Testing Banking Applications
• Design & implement functional UI tests for a Banking App
• Conclusion
NOTE: All trademarks, logos and brand names are the are property of their respective owners. All company, product and
service names used in this presentation are for identification purposes only. Use of these names, trademarks and brands
does not imply endorsement.

What is a Banking Application?
• A banking application is a software (mobile, web, and desktop)
that manages financial data and provides money transfers.
• Banking applications allow users to
• view current balances
• view transactions history
• transfer funds to other bank accounts
• schedule payments
• …

Characteristics of Banking Applications
• Banking applications are considered the most challenging
applications in the software industry, both on development and
testing side.
• Banking applications have a complex architecture (design and
technology), complex business workflows, and a wide range of
features dealing with confidential financial data.

• Supporting thousands of concurrent user sessions
• Working on multiple platforms and devices
• Processing fast and secure transactions
• Integrating with several applications like trading accounts, billing
apps, credit cards, etc.

• Handling complex business workflows
• Handling huge storage system (database)
• Troubleshooting customer issues through robust reporting & auditing
capability
• …
Banking is a constantly changing world due to frequently changing of banking
and government regulations.

Testing Banking Applications
• Testing banking applications requires end-to-end testing, starting from the UI
layer down to the underlying services, components and databases, involving
several software testing techniques such as:
• Functionality Testing
• Graphical User Interface Testing
• Cross Browser/Compatibility Testing
• Performance Testing
• Security Testing
• Database Testing
• Usability Testing
• …
To ensure quality of:
 business workflows &
functionality
 application security
 data integrity
 system performance
 application compatibility
 user experience
 ...

Functional UI Testing of Banking
Applications
• User Interface (UI) +
functionality testing are a very
important part of testing a
banking application.
• Functional UI Testing allows
verifying a web application end-
to-end, from beginning (the user
interface) to end (the database
layer) as a user would use it.

What is Functionality Testing?
• Functionality testing (aka functional testing) verifies that all
the functionality of the application being tested operate in
conformance with their specification.
• Verify that the application does "what" is supposed to do.
• Functionality testing uses black-box techniques
• NO knowledge of the internal web application logic
• Tests are derived from the specification
• Functionality testing includes several testing types such as unit,
smoke, sanity, integration, system, and regression tests.

What is User Interface Testing?
• UI Testing is the process of verifying the application’s user interface
• to determine that it satisfy specified (and implicit) requirements
• to demonstrate that it is fit for purpose
• to detect defects
• UI tests check an application via the user interface, in the same way
an end user would.
• UI tests mimic user's actions such as clicking on a control, entering
text, scrolling a page, … checking that the software/UI does what it
should.

Design Functional UI Testing: the BPER
case
• Use case: testing the BPER Smart Web© home banking
application (https://www.bper.it/), by performing, after logging
in, a wire transfer.

• To start writing your test, think about
what a user would do to perform a bank
transfer:
First she would have to navigate to the BPER
Smart Web© page. Once there, she would
login into the banking application. Next, after
navigating to the wire transfer page, she would
enter the beneficiary data (name, bank account
number, etc.), the amount and the description
of the bank transfer. After verifying the amount
and other details on the wire transfer summary
page, she would submit for final action of fund
transfer.
Design Functional UI Testing: the test use
case

• The test case will result in the following steps:
1. start browser and navigate to BPER Smart Web© website
2. enter username and password and login
3. navigate to the fund transfer page
4. enter Name and IBAN (bank account number) of the beneficiary
5. enter Amount and Description of the credit transfer
6. recap and verify the transfer data
7. transfer money and check the operation result
Design Functional UI Testing: the test steps

Design Functional UI Testing: a
simple test case format
Test Step (/input) Expected Output
1. Navigate to the BPER page at
https://homebanking.bpergroup.net/
The login page is opened.
2. Enter valid Username  "12345678" The username field is filled with the value “12345678“.
3. Enter valid Password  "12345678" The password field is filled.
4. Click “Accedi a Smart Web” (Sign in) button
The user is logged in and the bank account main
page/view is displayed.
5. Navigate to the Fund Transfer page The Fund Transfer page is displayed.
l
o
g
i
n

Design Functional UI Testing: a
simple test case format
Test Step (/input) Expected Output
6. Enter the beneficiary Name  "Maveryx srl"
The "Nome, Cognome o Intestazione Azienda"
(beneficiary name) field is filled with the value
"Maveryx srl".
7. Enter the beneficiary IBAN 
"IT76O0326803402052837088040"
The "IBAN" (beneficiary IBAN) field is filled with the
value "IT76O0326803402052837088040".
8. Enter the bank transfer Amount  "100"
The "Importo" (amount) field is filled with the value
"100".
9. Enter the bank transfer purpose/description 
"this is a test credit transfer"
The "Causale" (purpose/description) field is filled with
the value "this is a test credit transfer".
10. Click "Continua" to proceed Bank transfer successfully completed.
B
a
n
k
t
r
a
s
f
e
r

Design Functional UI Testing: test
automation
• To automate it, we will use
MAVERYX and Java.
• MAVERYX is an automated
functional testing and regression
testing tool. This software
provides automated testing
capabilities for functional,
regression, GUI, data- &
keyword-driven testing.
• It supports a range of
applications, including web-
based, .NET, Java, and more.

/* start Chrome browser */
Bootstrap.startApplication("Chrome");
GuiText browser = new GuiBrowser();
/* navigate to the BPER Smart Web website */
browser.navigateTo("https://homebanking.bpergroup.net/wps/portal/hb/home/ibpr/sec
/login/login");
/* check the login page URL */
assertEquals("https://homebanking.bpergroup.net/wps/portal/hb/home/ibpr/sec/login
/login", browser.getPageURL());
Assertions (like assertEquals) are truths about our software we may want to check.
Test script analysis: Navigation

/* the Username text field */
GuiText username = new GuiText("Inserisci il tuo Codice
Utente/Alias");
/* check the Username text field is editable */
assertTrue(username.isEditable());
/* enter username */
username.setText("12345678");
/* check the Username text field has the entered username */
assertEquals("12345678", username.getText());
//...the same for entering the password...
/* click sign in button to login */
new GuiButton("ACCEDI A SMART WEB").click();
Test script analysis: Login

Test script analysis: Enter data & Perform
credit transfer
/* Insert the beneficiary name */
new GuiText("Nome, Cognome o Intestazione
Azienda").setText("Maveryx srl");
/* Insert the beneficiary IBAN (bank account number) */
new GuiText("IBAN").setText("IT76O0326803402052837088040");
/* Enter bank transfer amount (€100) */
new GuiText("Importo").setText("100");
/* Enter bank transfer purpose/description */
new GuiText("Causale").setText("this is a test credit transfer");
/* Click continue button to perform the bank transfer */
new GuiButton("Continua").click();
/* Check the successful operation result*/
new GuiLabel("Operazione completata con successo!").waitFor(3, 1);

Design Functional UI Testing: invalid test
cases
• Starting from this test, you can create other (invalid) tests:
1. enter invalid username and/or password for login → sign-in error
2. enter invalid beneficiary IBAN  account number error

Design Functional UI Testing: invalid test
cases
3. enter invalid beneficiary name  name-account mismatch error
4. enter invalid amount (negative amount, amount greater than available
balance, ...)  transfer amount error
5. enter empty description  missing transfer description
6. …

Conclusion
• Banking applications are critical as they involve millions of transactions
with real money and confidential financial data.
• Testing banking applications goes end-to-end through the entire system
(from UI to underlying services and database). Functional UI tests act just
like users would if they were using the system.
• Testing banking applications includes
• load & performance testing
• security testing
• usability testing
• functional testing
• ...

Testing Banking Applications. Here is a practical example

Recommended

Recommended

More Related Content

What's hot

What's hot (18)

Similar to Testing Banking Applications. Here is a practical example

Similar to Testing Banking Applications. Here is a practical example (20)

More from Maveryx

More from Maveryx (8)

Recently uploaded

Recently uploaded (20)

Testing Banking Applications. Here is a practical example