give 5 test cases accourding the format of IEEE 827 OF OFFLINE BANK MANAGEMENT SYSTEM .PLEASE DO REPLY AS SOON AS POSSIBLE.

SEND THOSE OFFLINE BANK MANAGEMENT TEST CASES URGENTLY.

test cases for offline banking system

What is internet banking?

Internet banking makes use of electronic payment method that enables both the customers and financial institutions to pursue money transactions through the website. Nowadays, more people are interested in internet banking as it is faster and easier method of payment. One need to go to bank and stand in long queue to make financial transactions. Through internet banking, user can transfer and receive money, pay bills, initiate fixed deposits, perform demat transactions and the like.



Challenges In Testing Internet Banking Applications:

Different internet connections and browsers- Customers would login from different system and different browsers, like Mozilla, IE, Google chrome, Opera and the like. Also, user would be using different operating systems. Internet connections is yet another parameter. Software testing need to consider all these factors – browsers, Operating systems, internet connections and thorough testing need to be done. Page performance and all functionalities need to be tested thoroughly to ensure that customer can continue to operate the system smoothly.

Time to market – banks are constantly in a rush to update new features to entice customers. This might result in less time to test the application. This may seriously affect the quality of the internet banking application.



Different Types Of Testing In Internet Banking Applications:

Usability testing – Internet banking application would be used by many users- some would be technically sound and others may lack technical skills. Application should be simple so that even people who are not so much into technical side should be able to handle the application well. Website need to be tested for simple and efficient design so that any user would be able to navigate through internet banking application without assistance.

Security testing – Banking applications are the key targets of hackers and groups that commit fraudulent activities. Vulnerability scanning and penetration testing can reveal proliferation of defects and further system susceptibilities.

Functional testing – functional testing encompasses checking for all the requirements and specifications

Performance testing – Some days may have spike in banking activities – especially in festivals or period during which there is an offer. Performance failures can affect the reputation of the financial institution badly.

Database testing – This needs to be done to make sure that ensure that data integrity, data migration, validation and rules testing is fine.

UAT testing– This is the final phase in testing internet banking applications



Best Practices That Can Be Adopted For Regression Testing Of Online Banking Application:

In each release, business critical scenarios need to be tested in multiple cycles to make sure that functionalities are working as per the expectation.
Browser testing need to be done – for example Google chrome, Mozilla Firefox, Opera, IE and the like. Version testing also need to be done. Testing also need to be done in android and iOS devices to make sure that user interface is stable across all platforms.
Test cases need to be reviewed and modified after each release according to the new functionalities and changes.
If any defect is identified in production, that scenario need to be incorporated into the test scenario to make sure that issue will not occur in future releases.
Shakedown testing need to be performed after every build to make sure that environment is stable.
Latest versions of supporting tools and internal banking tools need to be tested that online banking application works fine across all platforms.
Once a defect is raised, it need to be captured and logs need to be attached. This would make it easier for the development team to analyze the root cause.
Major functionalities need to be tested after signoff till release to make sure that every functionality is working as per the expectation.
Clarification documents and emails need to be saved to make it useful for future releases.
Previous release learning or functionality need to be documented in a shared document.
Different types of test data needs to be saved in a shared document.
It would also be good if you have test data set up process in a shared location so that people in team can refer to and understand