qwertyuiopasdfghjklzxcvbnmqwertyui

opasdfghjklzxcvbnmqwertyuiopasdfgh
jklzxcvbnmqwertyuiopasdfghjklzxcvb
nmqwertyuiopasdfghjklzxcvbnmqwer
TEST REPORT
tyuiopasdfghjklzxcvbnmqwertyuiopas
GROUP--2

dfghjklzxcvbnmqwertyuiopasdfghjklzx
SYSTEMS & OPERATIONS

cvbnmqwertyuiopasdfghjklzxcvbnmq
wertyuiopasdfghjklzxcvbnmqwertyuio
pasdfghjklzxcvbnmqwertyuiopasdfghj
klzxcvbnmqwertyuiopasdfghjklzxcvbn
mqwertyuiopasdfghjklzxcvbnmqwerty
uiopasdfghjklzxcvbnmqwertyuiopasdf
ghjklzxcvbnmqwertyuiopasdfghjklzxc
vbnmqwertyuiopasdfghjklzxcvbnmrty
uiopasdfghjklzxcvbnmqwertyuiopasdf
ghjklzxcvbnmqwertyuiopasdfghjklzxc
vbnmqwertyuiopasdfghjklzxcvbnmqw
ertyuiopasdfghjklzxcvbnmqwertyuiop
TEST REPORT

Product/Project Insurance Management system

Version
Build no
Build date

1 INTRODUCTION

The purpose of this document is to plan and document the

complete activities required for the testing of Insurance Management
system.

2 SCOPE

The scope of the test is to cover all the vital aspects like tests proposed, assignment of
personnel, schedules, bug reporting and tracking etc.

3 TEST PERIOD

28TH JANUARY 2011—2.15PM TO 4.45PM

4 INPUT DOCUMENTS/REFERENCES

The basic input for system tests is the Software Requirement Specification(SRS) and
project report.

5 TESTS CONDUCTED

The tests planned include the following types:-

1. Functional tests
2. Usability tests(Beta Testing)
6 Test Environment

MCA LAB- SSTM –COCHIN

7 Test approach and test data

Test cases shall cover both positive and negative cases. The test cases prepared shall
be reviewed for correctness and completeness. A mapping of these against the functions
depicted in the SRS shall also be done to ensure the required coverage. Based on the final
reviewed test cases, test execution shall be done on a separate test environment created
exclusively for this purpose. Testing is done and the results are noted in the test reports. After
the testing is over, these are reviewed once again. Bugs shall be identified, classified
(critical/major/minor) and reported.

8 Test results and findings

 The navigation to each and other pages are done properly.

 The data type each field is not mentioned properly.
 On wrong data entry, there is no option for re-entry or edit option.

8.1 Modules tested

HOME PAGE

 Contains only relevant details arranged in proper order.

REGISTRATION PAGE

 No specific format for customer id.

 Name accepts both alphabets and numeric characters.
 Mandatory columns are not marked.
 Mobile number less than character size=10 is also accepted.
 It was not showing whether the id is available or not.

REGISTER POLICY PAGE

 All the Text boxes should be un editable

  The vehicles in the parking yard are not listed automatically, needed to click
on “search” button to get the list.
 Also Refreshing of the list is also not happening after a delete unless the
“Search” button is clicked
 Yard no. is not getting cleared once deletion is done

VIEW POLICY PAGE

 Error messages are not understandable by user.

8.2 Defect statistics and Metrics

S.No Sub module No of test No of defects Critical Major Cosmetic

cases
executed

1 HOME PAGE 8 No Defects - - -

2 REGISTRATION 30 9 3 2 3

3 REGISTER 3 1 - - 1
POLICY

4 VIEW POLICY 4 1 - - 1

5 REMIT 5 1 - - 1

6 Settings 4 1 - 1 -

TOTALS 54 13 3 3 6

8.3 Suggestions for improvements

 The data type for each field can be mentioned clearly

 On wrong data entry it can ask for re entry
 The error messages should be understandable to the user
  Compulsory fields can be specified by *

Prepared by Group2
Date 02/02/2011
Approved by
Date