Name: Umesh Mahajan

Roll No. : SYMCA2105

PRN: 121M1H005

Assignment 1: Test Plan for E-Banking application

1. Background

This gives the background of the project. E-banking application allows users to perform basic
operations of banking online. In this internet era where everything is accessible online, this
application provides some basic banking services online using this e-banking application.

2. Introduction

This application provides basic banking services to the end users like viewing bank details,
viewing last transaction history, and money transfer. This application will drastically reduce the
need for standing in the queue waiting for their chance just to get done a simple task.

3. Assumption

This is assumed that the end user is well versed with using online based applications.

4. Test items

● Money transfer
● Account transaction history
● Account balance view
● User Authentication

5. Features to be tested

● User authentication
● User identification
● Account balance
● Account transaction history

6. Featured not to be tested

None ( Since this is a banking system and we have to ensure that we don’t leave any thing
untested which can in future become a reason for data theft or other things)
7. Approach

We will be using manual and automated testing for this application as well in regards with test
strategies we will used black box and white box testing. Other tests performed on this
application are performance testing, stress testing, load testing, regression testing etc.

8. Item pass/fail:

User account number must take only integer numbers

The input used in the money transfer section must only contain positive numbers.
Account transactions must be correct
(If both the expected and actual output is same then the result is pass)

9. Suspension:

Some team members may leave the project/organization in between. Also there might be the
instance that the project has overshot the given time or it has exhausted all the money allocated
to the project.

10. Test deliverables:

The reports will be checked for each test whether it is passed or not.

11. Testing task :

Various testing tasks will be created according to the scenario and will be assigned to various
testers.

12. Environment needs:

The user must have a computer or mobile device with a good internet connection. The user
must also have a bank account

13. Responsibilities:

It is the responsibility of the individual to complete the test task given to them and take care of
the reporting.

14. Staffing and training:

The staff must be trained on manual and automation testing. They must be provided training on
testing tools.

15. Schedule:

Describes the schedule in which the project has to be completed. This can be a project of 2-3
months.

16. Resources:

● Testers
● SRS
● Money

17. Risk and contingencies:

Team members leave in between and the money allocated to the project gets exhausted in
between.

18. Approvals:

Team members must take approval from the QA manager for every defect.