Testing Checklist for Banking Website
2017
Testing Checklist for Banking Website
QA Specialist TestOrigen Software Testing Pvt. Ltd. 1/1/2017
WWW.TESTORIGEN.COM
PAGE 1
Testing Checklist for Banking Website
Business Scenario Tests: Admin Test Cases:
Tested by
Tested on
Pass or Fail
Remarks
1. Check Admin login with valid and Invalid information 2. Check administrator login without information 3. Check all administrator home links 4. Check administrator password with valid and invalid information 5. Check administrator password without information 6. Check administrator password with existing information 7.
Check administrator logout
Clients & Visitors Test Cases:
Tested by Tested on Pass or Fail Remarks
1. Check all visitor or customer links 2. Confirm clients login with valid and invalid information 3. Confirm clients login without information 4. Confirm bankers login without information 5. Confirm bankers login with valid or invalid information
WWW.TESTORIGEN.COM
PAGE 2
Testing Checklist for Banking Website
New Branch Test Cases:
Tested by Tested on Pass or Fail
Remarks
1. Test new branch with valid and invalid information 2. Test new branch without information 3. Test new branch with existing branch information 4.
Test reset and cancel alternative
5. Test Refresh branch with substantial and invalid information 6. Test Refresh branch without information 7. Test Refresh branch with existing branch information 8.
Check cancel alternative
9. Check branch deletion with and without conditions 10. Confirm branch search choice
New Role Test Cases:
Tested by
Tested on
Pass or Fail
Remarks
1. Test new role with valid and invalid information 2.
Test new role without information
3. Test new role with existing information 4.
Test role portrayal and part sorts
5.
Test cancel and reset alternative
6. Test role cancellation with and without dependency 7.
Test links in role details page
WWW.TESTORIGEN.COM
PAGE 3
Testing Checklist for Banking Website
New Client Test Cases:
Tested by
Tested on
Pass or Fail
Remarks
1. Test a new client with valid and invalid information 2. Test a new client without information 3. Test a new client with existing branch information 4. Confirm cancel and reset alternative 5. Refresh client with valid and invalid information 6. Refresh client with existing information 7. Confirm cancel alternative 8. Confirm deletion of the client
Database Testing: Organized Database Test Cases :
Tested by
Tested on Pass or Fail Remarks
1. Test The Name of the database. 2. Test the Name of the log document. 3. Test the Disk space portion for databases. 4. Test the Names of all tables, sections, and their sorts. 5. Test the Invalid value checks. 6. Check keys, files, and data types of columns utilized.
WWW.TESTORIGEN.COM
PAGE 4
Testing Checklist for Banking Website
Functional Database Test Cases:
Tested by
Tested on Pass or Fail Remarks
1. Test the events causing the triggers 2. Test the Functions inside stored methodology and conceivable combinations. 3. Test the End to end data flow beginning from the front end to the backend.
Non-Functional Database Test Cases:
Tested by Tested on
Pass or Fail
Remarks
Tested by Tested on
Pass or Fail
Remarks
1. Make test scripts for significant elements and utilize them for regression testing at regular intervals. 2. Compose tests that track bugs in log records. 3. Change information in backend tables and watch the impact on the frontend. 4. Insert invalid values from the backend and watch the impact.
ATM Transactions Test Cases: 1. Load test Balance inquiry 2. Load test Cash withdrawal 3. Load test Cheque Deposit 4. Load test Cash Deposit
WWW.TESTORIGEN.COM
PAGE 5
Testing Checklist for Banking Website
Core Banking Test Cases:
Tested by
Tested on
Pass or Fail
Remarks
1. Test the Customer Search to pull subtle elements 2. Test the Open account 3. Test the Deposit or pull back money 4. Test the View exchange subtle elements 5. Test the Quick loan apply 6. Test the Issue of Banker's Checks, Drafts and Warrants
Loan Processing Test Cases:
Tested by
Tested on
Pass or Fail
Remarks
1. Test the client profile for retail or corporate loan 2. Oversee security master details 3. Test the Send loan information to the central office as well as to branches 4. Test the loan applications 5. Create different records; for example, sanction letter, proposal note and so forth. 6. Transfer supporting records 7. Confirm, Sanction/Reject loans based progressive system
WWW.TESTORIGEN.COM
PAGE 6
Testing Checklist for Banking Website
Usability Testing: UI Test Cases:
Tested by
Tested on
Pass or Fail
Remarks
1. Test the balance inquiry is executing in under 5 seconds 2. Test the business exchange running fast without timeout issues, during peak hours 3. Is your client support group getting calls about client dissatisfaction in accessing the banking application? 4. Test the ATMs effectively handling each and every exchange without defects and in the fastest time 5. Is your loan processing executive happy with the speed of the applications, while pulling different client information? 6. Test all the servers and applications, up and running without any downtime. 7. Test the applications performing quick for on the web and group operations. 8. Test the equipment utilized by you limit in an advanced way 9. Test the, How many number of times application or database restarted?
WWW.TESTORIGEN.COM
PAGE 7
Testing Checklist for Banking Website
Security Testing: Penetration Test Cases:
Tested Tested Pass or by on Fail
Remarks
1. Attempt to specifically get to bookmarked page without login to the framework. 2. Check that past accessed pages should not available after log out i.e. Sign out and after that press the Back button to get page accessed before. 3. Check the valid and invalid passwords 4. Check Is Right Click, View, Source debilitated? Source code should not be visible to client. 5. Check the timeout condition, after timeout client should not ready to explore through the site. 6. Check Are you prevented from doing direct searches by altering content in the URL? 7. Check that limited page should be available by client after session time out. 8. ID/password authentication strategies entered the wrong password a few times and check if the account gets locked. 9. Confirm that Error Message does not contain pernicious data with the goal that programmer will utilize this data to hack site.
WWW.TESTORIGEN.COM
PAGE 8