Online Banking Test Cases describes the process of preparing test cases for an online banking system. This process involves identifying the different features and scenarios that the system supports and creating test cases that cover each of these scenarios.
To prepare test cases for an online banking system, you can follow these steps:
Understand the system requirements: Review the system requirements document to understand the functionality of the system and the different features it provides.
Identify testable scenarios: Identify different scenarios that can be tested, such as account registration, login, account management, money transfer, bill payments, and transaction history.
Create test cases: For each testable scenario, create a test case that outlines the steps needed to test the scenario, the expected outcome, and any prerequisites or conditions that must be met.
Define test data: Define the test data that will be used for each test case, including valid and invalid input values.
Identify test environment: Identify the test environment, such as the operating system, browser, and device that will be used for testing.
Define test execution steps: Define the steps that need to be followed to execute each test case, including any setup steps, test steps, and cleanup steps.
Create test scripts: Create test scripts that automate the execution of test cases, if needed.
Review and prioritize test cases: Review the test cases to ensure that they are complete and accurate, and prioritize them based on the criticality of the functionality they are testing.
Execute test cases: Execute the test cases and document the results, including any issues or defects that are identified.
Review and update test cases: Review the test cases and update them as needed based on the results of testing and any changes to the system requirements.
It’s important to note that testing an online banking system requires a great deal of care and attention to detail, as well as a good understanding of security and compliance requirements.
Login Page
Test Case Id
Test Condition
Test Data
Expected Result
Actual Result in Test Cycle / Description
1
Blank User Name and blank password.
System should display message “Enter User Name and Password”
Ok
2
Enter User Name and Blank password
System should display message “Enter Password”
Ok
3
Enter blank User Name and password
System should display message “Enter User Name”
Ok
4
User enter wrong User Name and password
System should display message “Wrong User Name and password, can not login”
OK
5
User enter correct User Name and password
Data from CustMaster
System should redirect to default.aspx
OK
Home Page
Test Case Id
Test Condition
Test Data
Expected Result
Actual Result in Test Cycle / Description
1
Check welcome message
System should display currently logged user name and Change Password, Logout Link
Ok
2
User Login
CustMaster
System should display navigation link for my Account, Fund Trasfer
Ok
3
Check Navigation Link.
System should display link to open/navigate the page
Ok
Change Password
Test Case Id
Test Condition
Test Data
Expected Result
Actual Result in Test Cycle / Description
1
Enter blank old password.
System should display message “Old Password can not be blank”
Ok
2
Enter wrong old password.
System should display message “Wrong old Password can not change password”
Ok
3
New Password and confirm password are not match
Password=123 Confirm Password=1234
System should display message “Password and confirm password does not match”
OK
4
Enter all valid information
System should display “Password changed successfully” and redirect to my account page.
OK
New Payee
Test Case Id
Test Condition
Test Data
Expected Result
Actual Result in Test Cycle / Description
1
Admin enters blank payee name and press save button.
System should display message “Enter payee name”
Ok
2
Admin enters duplicate account number and press save button.
System should display message “Duplicate account number”
Ok
3
Enter all valid information
System should display “Record is saved” and display payee details in grid.
