Enterprise software testing

ASSIGNMENT COVERSHEET
SUBJECT NUMBER & NAME
32571
Enterprise Software Testing
NAME OF STUDENT(s)
SURNAME FIRST NAME
STUDENT ID(s)
Amxxxx xxxx 1xxxxx
Mohammad Emon 12794121
ASSESSMENT ITEM NUMBER
Assignment 2-Final Report
NAME OF TUTOR
Tejbir Chopra
GROUP Name And ID
Sydney IT Testers(8)
Tutorial day and time
Monday and 6 PM
I confirm that I have read, understood and followed the guidelines for assignment submission and presentation.
I confirm that I have read, understood and followed the advice in the Subject Outline about assessment
requirements.
I understand that if this assignment is submitted after the due date it may incur a penalty for lateness unless I
have previously had an extension of time approved and have attached the written confirmation of this extension.
Declaration of originality: The work contained in this assignment, other than that specifically attributed to another
source, is that of the author(s) and has not been previously submitted for assessment. I understand that, should
this declaration be found to be false, disciplinary action could be taken and penalties imposed in accordance with
University policy and rules. In the statement below, I have indicated the extent to which I have collaborated with
others, whom I have named.
Signature of student(s) ____________________________________________________________ Date _________________________

Tittle: Browser Testing of Bank

3
Group 8: Sydney IT Testers
Table of Contents
1.1 Purpose:................................................................................................................................................... 4
1.2 Audience: ................................................................................................................................................ 4
1.3 Requirement and Scope .......................................................................................................................... 4
1.4 Test specifications:.................................................................................................................................. 5
As a customers test cases specification described below tables: ............................................................. 8
As a webservices test cases described in following table:...................................................................... 10
1.5 Test Estimation: .................................................................................................................................... 11
1.6 Test Work Planning ............................................................................................................................. 13
1.7 Bug report or issue management :........................................................................................................ 16
1.8 Reporting............................................................................................................................................... 28
1.9 Information needs: ............................................................................................................................... 29
Suspension criteria:................................................................................................................................ 31
Exit Criteria: ............................................................................................................................................ 32
2.0 Critique: ................................................................................................................................................ 33
References................................................................................................................................................... 35

4
1.1 Purpose:
This test plan explain the testing approach and summary of the testing of the test plan in combank
version 4. This document includes:
• Test strategy describes the project start and end date , testing technique, test cases , and time
estimation.
• Execution strategy rules such as how test Will be executed and find & report all defects and fixes.
• Show the management process such as communication, team roaster , improvements etc.
1.2 Audience:
The major audience is the project manager who is plan for the testing activities and at the end review the
documents. Besides also, track the performance of the test and later stage approve the document.
The stakeholders representatives and participants may concerned about the verify that its aligned with
business goals of the test.
On the other hands, technical team make sure the test plan and deliverables are aligned ,and follow the
exact procedure to fixes the bugs. Lastly, business analyst will help to provide inputs any functional
changes
1.3 Requirement and Scope
The primary requirement of the test is:
1)All application pages must load and display correctly.
2)All URL links on each page must correctly load the linked page.
This the primary requirement which is required mandatory to check the function of the browser. The
scope of this project is testing the function, usability, and compatibility.

5
1.4 Test specifications:
Provide a template or example test specification for each test technique that has been identified
1) Ask client for as many project related documents as possible.
2) Requirement walkthrough gave us an opportunity to raise defects in the requirement phase itself
which was cheapest to fix.
Project Name: CommBank
Test Case
Test Case ID: BU_001 Test Designed by: <Name>
Test Priority (Low/Medium/High): Med
Test Designed
date: <Date>
Module Name: Bank login screen Test Executed by: <Name>
Test Title: Test the Login Functionality in Banking
Test Execution
date: <Date>
Description: Verify login with valid username and
password
Step Test Steps Test Data Expected Result Actual Result
Status
(Pass/
Fail)
Notes
1
Navigate to
login page User should be
able to login
User should is
able to login
Pass
2
Provide
valid
username
User= exampl
e@gmail.com
Credential can be
entered
As Expected Pass
3
Provide
valid
password
Password:
1234
Credential can be
entered
As Expected Pass

6
4
Click on
Login button
User logged
User logged
successfully
Pass
Post-conditions: User is validated with database and successfully login to the account.
The account session details are logged in the database.
System Test Plan: More details provide below table as manager level modules

8
As a customers test cases specification described below tables:

10
As a webservices test cases described in following table:

11
1.5 Test Estimation:
Table below described the effort required for the test
No. Module
Name
ApplicableR
oles
Description Weightage
1. Balance
Enquiry
Manager
Customer
Customer: An individual
customer cab have multiplayer
accounts.And also view balance
for his personal account only.
Manager: Manager is person
who can view balance of all the
customer under his authority.
3
2. Fund
Transfer
Manager
Customer
Customer: Customer can able to
transfer funds to any destination
from his own account.
Manager: Manager can transfer
funds to any destination account
from any source of bank
accounts.
5
3. Mini
Statement
Manager
Customer
It’s shows recently last 5
transactions of the account.
Customer: customer can only
able to see his ow personal mini
statement
Manager: Manager can access
to any mini statement
3
4. Customized
Statement
Manager
Customer
Which is allow to filter and show
transactions of the account by
specific date ,transaction value
Customer: only can see his own
personal customise statement for
his account .
Manager: manager can access
to any statement account
5

12
5. Change
Password
Manager
Customer
Customer: change password for
only accessible for customer point
of view
Manager: But manger can
change password for only his
account .he is not allowed to
change any customers password
1
6. New
Customer
Manager Manager: A manager can add a
new customer. Manager has the
ability to ass new customers.
Manager: He can edit the details
such as address, email and
mobile numbers of customers
3
7. New
Account
Manager customer are allowed to create
multiples savings accounts and or
he can have multiple current and
saving accounts.
Manager: Manager can able to
add new account for existing
customer
5
8. Edit
Account
Manager Manager: He can edit account
for existing account holders.
1
9. Delete
Account
Manager Manager: Manager can able to
delete any customers account
1
10. Delete
Customer
Manager Customer deleted automatically if
not activities on current or saving
account
Manager: Manager can delete
customer any time
1
11. Deposit Manager Manager: A manager can deposit
money into any account. Usually
done when cash is deposited at a
bank branch.
3
12. Withdrawal Manager Manager: Manger can withdraw
money from any account and its
is done when cash is withdrawn at
bank branch
3

13
STEP B) Estimate duration for the task:
After finishing the classifying the function points, we have to build the duration for the test.
So it is describe by how much time needs to Finnish the task.which calculated by following
formula
• Total Effort: the effort is need to test all the functions of the online site
• Total Function Points: Total modules of the website
• Estimate defined per Function Points: The average effort to complete one function
points.
Let’s say our project team is estimated as function points of 5 hours/ points.And then
estimate the total effort to test al the functions of the site is described by following table.
Weightage # of Function Points Total
Complex 5 3 15
Medium 3 5 15
Simple 1 4 4
Function Total Points 34
Estimate define per point 5
Total Estimated Effort (Person Hours) 170
1.6 Test Work Planning
After now the project beginning to start, then assigned the test the ‘comm bank’ website. And then we are
making test cases vey carefully . So if there any previous record or document have the client should
provide it.It must follow the the software testing life cycle(STLC).But sometimes its not possible due
to manpower, budget and time limitation.

14
Automation testing run by using selenium web driver for cross browser testing and web link checker used for check any broken
links.so the following step described below.
1)First to the development teams informs the release of 1st
version of the banking site, so it will implement the following
modules for the manager.
• New Customer
• Edit Customer
• New Account
• Edit Account
• Delete Account
• Delete Customer
• Mini Statement
• Customized Statement
2)Then it gives us a start to build Test cases. Test case build for the 8 manger module which is mentioned above.
So its looks such as more like unit test cases and run by the developers.But in practical the developers due to time
limitation they only focus test the system rarely throughly.So its better to check all the unit test cases.
So in our project we included the unit test cases.
Integration Testing
This test focus on checking the data communication of the test cases.
Let’s now pin point ours test cases cases.So after, First version of website is available for test,Execute test cases.
And then bug should be transfer into the spreadsheet format.
So after that the testers found the bugs in defect tracker spreadsheet. There is lot of bugs which is found.then it reported to the
development team and they add the balance inquiry module for this release and build unit test plan for the balance enquiry
module.
If The report of all integration test case is down, the project schedule will be delayed.That why need to execute the smoke
testing,before the starting ting test execution.
So we observed there is large number of test cases are lagging in the unit test plan.Afterwards, we run the unit test cases.
After finding bugs , it delivers to the developers to fix the bus in named version 1 of the report. And added balance enquiry
module to version 2. After get respond from the developer, rerun the failed test cases.
In next step, we updated on version 2 of the site, such as integration test cases, unit test cases and bug report version 2.
After this step, the development team informed that after next two days version 3 will be available such as modules for the
manager and customers roles
Then the build and run the module test case for
Manager Role:
1. Change Password
2. Deposit
3. Withdrawal
4. Fund Transfer
Customer Role:
1. Balance enquiry
2. Fund Transfer
3. Mini Statement
4. Customized Statement

15
5. Change Password
Then perform integration test for all modules.This is time consuming process is typically performed by a tea of 5 members
After this step, nest phase is building system test plan.It need now the Webservice and created test case to verify the
Websevices.
After this we updated to to version 3 of the report.and then rerun the failed test case and updated the bug report.
Last step , officials the the project is closed.

16
1.7 Bug report or issue management :
We have did 4 version of the report which show in the following table;

20
Version 2 of the report

24
Version 3 of the bug report

25
Version 4 of the report

26
Test Summary Report
Test planning Test execution
Release Date Planned Specified
Total
Estimated
Time Performed
Total
Actual
time Passed Failed
Version
1
07-
05-
2018
Verify All
pages are
work correctly
Check
the broken
links 20 hour 14 hours 24 passed
Version
2
10-
05-
2018
Determine
the tools to
improve the
testing 48 hour 30 hours 30 passed
Version
3
12-
05-
2018
Determine
the
compatibility
testing and
improve the
productivity
Check it
work on on
the
operation
system
and
improve
the testing
time
estiation. 48 hours 36 hours
35
hours passed

27
Quality Summary Report
Release defects Defects by type
Release Date
Defects
found
Defects
fixed
Total
defects
Severity
1
Severity
2
Severity
3
Severity
4
Severity
5
Version
1
7-05-
2018
Some
grammatical
and spelling
errors yes 84
Level 5
high
Version
2
10-05-
2018
Found
some link
not working yes 84
Level 4
medium-
high
Version
3
12-05-
2018
Content
display
error like
images and
size issues
and some
buttons yes 20
Level 3
medium
Version
4
19-05-
2018
Rerun the
test Yes 20
Level 3
medium

28
1.8 Reporting
The following Stakeholders should be reported in our project.Which described below table
Stakeholder Interest / Objectives
Business owner That the web pages continue to function
correctly so that their potential and actual
customers are not disrupted.
CIO the Check and responsible for system correction
on time and in the budget.
Project manager To determine what is given priority and more
important to test
Find the best tool and implement the best
technique for our testing process. Deliver the
testing project on time in budget.
Manage the whole project under his/her
supervision and define the direction.
Developers To develop the application as per the
requirement and minimise the effect of the
browser on a web application. Should be
compartable and easy to use.
Test Designer
Testers
Test Administrator
Do all test related activities. Identifying and
describing appropriate test
techniques/tools/automation architecture. Verify
and assess the Test Approach Execute the
tests, Log results, Report the defects. To
investigate that web pages are correctly linked, is
comparable to browsers, is the web pages
secured. Builds up and ensures Test
environment and assets
are managed and maintained Support Tester to
use the test environment for test execution
App users The end uses who potentially use the browser.

29
1.9 Information needs:
Information needs of each of the identified stakeholders are described. Information require for each stakeholders
are described below.so bear in mind that, when creating report who is it for and who will read it.So our potentials
audience are:
1)Technical users(test managers):
The interest the progress of the testing, and how any problem arises and how it is going to be saved.
And they give the description of the applied methods and technology to rank priority of importance.
2)Product Managers:
They are concerned about the implementation deadlines and the actual test results without needless
technical details.
3)Business users:
They are authority to make decisions after the end of testing.They also concerned about the quality of
the work finished and the final results which have to provide shortest and clearest format as concerned.
It’s also better to provide visual forms such as graphs and diagrams.Besides also recommendations
from expert opinion is if possible are needed.
Furthermore, test report can be breakdown into two types of relative to time such as intermediary and final.
Intermediary test report:
Which is show the progress of work and it is determined by comparing the state of the project on different
time intervals such as day, week, month. It is actually the progress status condition like which stage is now .
Version or iteration test report:
This type of reporting focus on the task were performed by the test team for specific of the product.
And the lastly, final report show overall view of dummy the work done.And it is better to give status of the
product and ,whether is tested fully or release version.
So , In the picture below test report plan information described.

30
Project information:
Which is mention the tittle, product name and version in the test report.
Test objective:
This section described the software testing process such as functional , performance etc.
Test Summary:
this is compulsory part which should includes the
the number of the execute test cases, the number of pass or fail rate percentage test cases and any
‘Comments’.
So another great way to report visually such as use color, graphs and highlighted tables for it.The picture
below show as examples
Defects:
This part should contains the total number of bugs, bugs statism number of bugs by each status(open,closed
or fixed). Severity and priority level . The picture below show examples.
•
We can also use the defects density metrics and percentage of fixed bugs. In the following picture
described below:
a) No. of test cases planned vs executed
b) No. of test cases passed/failed

31
c) No of defects identified and their Status & Severity
Suspension criteria:
It’s the method when the test is suspended until it will be fixed. It is measured by if 40 % of the test case
is failed, it will send back to the development team for fixes. In the figure below briefly explain the
process.
Example: If your team members report that there are 40% of test cases failed, you should suspend testing
until the development team fixes all the failed test cases.

32
Figure 1: Suspension and pass criteria of test
Exit Criteria:
It is representing the favourable completion of test which is measured by 95% of the test case must be a
pass.
There’s another way to measure exit criteria by mentioning the ‘run rate’ and ‘pass rate’. Achieving high
pass rate vital for project test success.
‘Run rate’ which is determined by dividing number of test cases executed. And total test cases.
On the other hand,’ pass rate’ determined by test case passed divided by test case executed.
Conclusion:
This part described as after the Exit criteria are met and then show demo of the testing by its called
“go live’’.

33
2.0 Critique:
Test project objectives and constraints reviewed:
As per the budget and resources we observes that all the proposed objectives cannot be accomplished. So
reproduced the objectives and drop the plan of testing website on mobile and tablet devices. It is too
costly and cannot achieve
Due to lack resources can not investigate tool, so as per the market review of available automation tool
we choose to use Selenium WebDriver for Automation Testing.
Recent 3 years versions of browsers have been tested.
Web browser to be tested on only Windows and Mac OS
Test strategy reviewed and potential improvements described:
Strategy at initial stage of project proposal was very amateur. As we worked on the project and start
progressing through testing proves, we realised that we need to change our strategy and we improved our
test strategy.
Reviewed Strategy:
1. Changed few techniques of testing and dropped performance testing.
2. Developed a plan to work on testing along with the progress of development of testing using agile.
3. Developed test cases as we go along with development of website.
4. Development team updated with 8 module of website at initial stage.
5. Tested test cases and created bug report for development team.
6. Integration testing has been done.
7. Second version of testing has been in progress along with one more module of website developed by
developer is been tested.
8. Developed bug report V2.
9. System test plan developed and tested.
10. One more module is been developed by developer.
11. Tested all modules and generated final bug report.
12. Final testing End-to-End testing is been done.
13. Developed final test report for stakeholders.
Test planning reviewed and potential improvements identified:
Sr
No
Problem Description
1 Quality Customer still found some Defect after release
2 Delivery The project was delayed
3 Team Some employees didn't co-operate with other team members
4 Skills Team member lacked desired skills to complete their tasks
5 Management
Test Manager did not monitor the progress well which caused some
project delayed
6 Communication
No constant contact with customer; misunderstanding the customer's
requirement
7 Cost The Project cost was overrun beyond set budget

34
Test reporting reviewed and potential improvements identified:
Reporting the primary purpose of the testing which is acquire by the final result of the testing and
submit to the stakeholders to make decisions.
Reviewed Reporting:
It is a technique which aim for the professional as mentioned do in the Industry requirement.The main
reason its developed for:
1.Best quality test report help to identify the current status of the test report
2. It’s helps to take ant correlated action ehh its necessary.
3.when the product is ready for release or not its depends of the test report.
In below described the Somme of important part.
1.Details
Details of all test activities should provided as soon as it’s executed.Another important notes is that not
include any abstract information into the report.
2. Clearness
In reporting have to make sure data and information clear and concise easy to understandable.
3. Standardisation
Always use standard universal templates for easy understandable for readers to review the test report.
5.Specification
When writing report always focus on the main points . No need to write an essay for the project every
section. Better to write as summary of the test specification.
There is now automatically test management tools available in the market which provide high
customised test report.
The sign of best reports should include the test cases, test runs, bug status, bug severity, bug priority,
crash and spent time reports.
Group project experience is reviewed and potential improvements identified:
As started with group of 5, we found lack of interest of 3 members, those who did not show up after
forming the group. It was very difficult throughout the project to complete each and every task and cannot
perform very well as per the requirement of the project.
Every week’s progress was discussed and achieved by 2 members where other group was in group of 5 to
6 members.
As we found out the issue, we 2 members in group co-operate with each other and divided the weekly
assignment. We both cooperate with each other and arranged meetings. Help each other to do our part of
assignment and reviewed before we present the peer review report.
As we go ahead with project, we build confidence in us to do well and successfully completed the
project.

35
References
fortifysolution, 2016. How To Fix Website Not Working Properly,Viewed 28th
april 2018
<http://notworking.us/website-not-working/>
Ghahrai, A., 2017. Web Application Testing Techniques,Viewed 30th
april 2018,
<https://www.testingexcellence.com/web-application-testing-techniques/>
guru99, n.d, How to Create a Test Plan,Viewd 1st
may 2018, < https://www.guru99.com/web-application-
testing.html>

Enterprise software testing

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Enterprise software testing

Similar to Enterprise software testing (20)

More from Mohammad Emrul Hassan Emon

More from Mohammad Emrul Hassan Emon (20)

Recently uploaded

Recently uploaded (20)

Enterprise software testing