PRJ/2013/IT/13

Testing

Testing

C.S.P.I.T

90

Department of Information-Technology

PRJ/2013/IT/13

Testing

Overview:
Software testing is a critical element of software quality assurance and represents the
ultimate review of specification, design, and code generation. As the project was fresh and
some technical risks were involved, testing played an important part in the process.

7.1 Testing Methodology

Testing is the process of executing the program(s) with the intention of finding out errors.
During testing, the program to be tested is executed with a set of test cases and the output of
the programs for the test case is evaluated to determine if the program is performing as it is
expected to be.

The success of testing in revealing errors in programs depends critically on the test cases. In
software systems the use of testing is not limited to the testing phase. The result of the testing
is used later on during maintenance also. During testing a test suite has been prepared, which
consists of various test case along with their expected output so that later on if the software is
modified the test case from the test suite can be used to see that modifications does not have
any undesirable effect.

Coding is the art of Construction. Testing is the art of Destruction. An Integral part of
Quality Assurance

C.S.P.I.T

91

Department of Information-Technology

PRJ/2013/IT/13

Testing

7.2 Testing Strategy

Levels of testing
Unit Testing.
Integration Testing.
System Testing.
Acceptance Testing

Clients Needs

Acceptance Testing

Requirements

System Testing

Design

Integration Testing

Code

Unit Testing

Figure 7.1 Levels of Testing

C.S.P.I.T

92

Department of Information-Technology

PRJ/2013/IT/13

Testing

7.3 Various Testing Methods

7.3.1. Unit Testing
In this testing user test the programs making up a system. For this reason it is also called a
program testing.
Unit testing can be performed from the bottom up, starting with the smallest and lowest-level
modules and proceeding one at a time or it can be performed from top down which begins
with upper level module. The checklist used by the organization for this level of testing is:Table of Checklist For Unit Testing

Test case Id
Nature of test

Unit Test

Description
Pre conditions
Test action

1. (default Page)
2. Fill up the following table.
Note:
Mandatory Field: Yes/No (Field is required or not)
Max Length to be checked: maximum length to be allowed. (E.g.
15)
Allowed Special characters: list all special characters, which are not
allowed. (Special characters are !, @, #, $, %, ^, &, *, (, ), +, {, }, [,
], \, |, ;, : ,, , ?, >, <, ., , ,/, -, _ etc.)
Email/Web site validation: Email / Web site
Alpha numeric /numeric/ Alphabets field validation: Alpha
numeric/Numeric/Alphabets
Single quote validation: Yes/No
Space validation: L/R/M (L-space not allowed on left side of filed
value, R- space not allowed on right side of field value, M- space not
allowed in between field value)

C.S.P.I.T

93

Department of Information-Technology

PRJ/2013/IT/13

Testing

Date validation: Yes/No (Field is date field or not)

3. Fill the record for the mentioned fields above and click on save
button.
Expected result

All validations mentioned in test action should work successfully.

Post conditions

List of newly added Root Causes should be displayed below in

listing.

Assumptions

Table 7.1 Unit Testing

7.3.2 Integration Testing

This testing strategy tests the integration of each module in the system. It also tests to find
discrepancies between the system and its original objective, current specification and systems
documentation. The preliminary concern is the compatibility of individual modules.
The checklist used by the organization for this level of testing is :-

Table Of Checklist For Integration Testing

Sr.
No
1

Result
Task / Activity

Y OK N Error N/A

Remarks

A master-detail relationship should be

maintained.

Is the user being redirected to the correct

page(s) after satisfying other modules
functionalities

Navigating is maintained between the

C.S.P.I.T

94

Department of Information-Technology

PRJ/2013/IT/13

Testing

modules.
4

Is the authorization and authentication

maintained?

Unit level functionalities should be

preserved after integration
Internal Integration the application interacts with the different
modules based on the hierarchy

Are messages shown for conflicting

actions?
External Integration External functionalities

Is the time difference being maintained

between our application & the external
application
Unidirectional

Is data being sent correctly from our end

to the external system
Bi-directional

Is data being sent correctly from our end

to the external system

10

Is data being received correctly at our end

from the external system

Table 7.2 Integration Testing

C.S.P.I.T

95

Department of Information-Technology

PRJ/2013/IT/13

Testing

7.3.3 System Testing

This testing strategy is performed by the QC who is not a part of the development team.
System Testing is further divided into three types of testing.

7.3.4 Functional Testing

QC does the functional testing of the system. QC tests whether the system satisfies all the
functions as specified in the SFRS, Prototype and the Test Cases.

7.3.5 Performance/Load Testing

Performance testing is a rigorous usability evaluation of a working system under realistic

conditions to identify usability problems and to compare measures such as success rate, task
time and user satisfaction with requirements. Major usability problems are identified that
may not be revealed by less formal testing, including problems related to the specific skills
and expectations of the users.

C.S.P.I.T

96

Department of Information-Technology

PRJ/2013/IT/13

Testing

7.4 Test Cases:

Master-Login Module:
Sr. No
1.

Test Case

Desired Behavior

Valid User Name, Valid

Redirect To Page of

Password

Citizen, Institute and

System Behavior
Valid

Report
2.

Invalid User Name, Valid

Stay on Master-Login

Password

Page, display Invalid

Valid

User-Name
3.

Valid User Name, Invalid

Stay on Master-Login

Password

Page, display Invalid

Valid

Password
4.

Invalid User Name, Invalid

Stay on Master-Login

Password

Page, display Invalid

Valid

Username and
password
Table 7.3 Test Case-1

C.S.P.I.T

97

Department of Information-Technology

PRJ/2013/IT/13

Testing

Citizen Registration Module:

Sr. No
1.

Test Case

Desired Behavior

All Inputs are Valid

Display Registration

System Behavior
Valid

Successful, Record
Stored in Database
2.

First Name/ Last Name not filled

On next tab show error

or incorrectly filled

message, Enter first

Valid

name and Last name

3.

Email Address not in proper

Show error in the next

format

tab, Enter valid email

Valid

address
4.

Password length not satisfied.

Show error, password

Valid

not long enough

5.

Passwords do not match

Show error, passwords

Valid

dont match
6.

Address fields missed

Show error, please fill

Valid

missing fields
7.

Contact Numbers incorrectly

Show error, please

filled

enter proper contact

Valid

numbers
8.

Check is removed from the terms

Show error, please

and conditions

check the terms and

Valid

conditions to proceed

Table 7.4 Test Case-2

C.S.P.I.T

98

Department of Information-Technology

PRJ/2013/IT/13

Testing

Institute Registration Module:

Sr. No
1.

Test Case

Desired Behavior

All inputs are valid

Redirect to Institute

System Behavior
Valid

username and
password page.
2.

3.

Registration number and license

Does not allow to store

number incorrectly filled.

the details

First Name/ Last Name not filled

On next tab show error

or incorrectly filled

message, Enter first

Valid

Valid

name and Last name

4.

Email Address not in proper

Show error in the next

format

tab, Enter valid email

Valid

address
5.

Password length not satisfied.

Show error, password

Valid

not long enough

6.

Passwords do not match

Show error, passwords

Valid

dont match
7.

Address fields missed

Show error, please fill

Valid

missing fields
8.

Contact Person name incorrectly

Show error, please

filled

enter proper contact

Valid

Person name.

Table 7.5 Test Case-3

C.S.P.I.T

99

Department of Information-Technology

PRJ/2013/IT/13

Testing

Doctor Registration Module:

Sr. No
1.

Test Case

Desired Behavior

All inputs are valid

Redirect to Doctor

System Behavior
Valid

username and
password page.
2.

3.

Registration Date incorrectly

Does not allow to store

filled.

the details

Username incorrectly filled

Does not allow to store

Valid

Valid

the details as first 4

characters should be
alphabet.
4.

Password length not satisfied.

Show error, password

Valid

not long enough

5.

Passwords do not match

Show error, passwords

Valid

dont match

Table 7.5 Test Case-3

C.S.P.I.T

100

Department of Information-Technology