chapter 7 testing

PRJ/2013/IT/13 Testing

C.S.P.I.T 90 Department of Information-Technology

Testing

7



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



7.2 Testing Strategy

Levels of testing

Unit Testing.

Integration Testing.

System Testing.

Acceptance Testing

Figure 7.1 Levels of Testing

Clients Needs

Requirements

Design

Code Unit Testing

Integration Testing

System Testing

Acceptance 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 !, @, #, $, %, ^, &, *, (, ), +, {, }, [,

], \, |, ;, : ,, , ?, >,



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 Task / Activity

Result Remarks

Y OK N Error N/A

1 A master-detail relationship should be

maintained.

2 Is the user being redirected to the correct

page(s) after satisfying other modules

functionalities

3 Navigating is maintained between the



modules.

4 Is the authorization and authentication

maintained?

5 Unit level functionalities should be

preserved after integration

Internal Integration the application interacts with the different

modules based on the hierarchy

6 Are messages shown for conflicting

actions?

External Integration External functionalities

7 Is the time difference being maintained

between our application & the external

application

Unidirectional

8 Is data being sent correctly from our end

to the external system

Bi-directional

9 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



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.



7.4 Test Cases:

Master-Login Module:

Sr. No Test Case Desired Behavior System Behavior

1. Valid User Name, Valid

Password

Redirect To Page of

Citizen, Institute and

Report

Valid

2. Invalid User Name, Valid

Password

Stay on Master-Login

Page, display Invalid

User-Name

Valid

3. Valid User Name, Invalid

Password



Password

Valid

4. Invalid User Name, Invalid

Password



Username and

password

Valid

Table 7.3 Test Case-1



Citizen Registration Module:


1. All Inputs are Valid Display Registration

Successful, Record

Stored in Database

Valid

2. First Name/ Last Name not filled

or incorrectly filled

On next tab show error

message, Enter first

name and Last name

Valid

3. Email Address not in proper

format

Show error in the next

tab, Enter valid email

address

Valid

4. Password length not satisfied. Show error, password

not long enough

Valid

5. Passwords do not match Show error, passwords

dont match

Valid

6. Address fields missed Show error, please fill

missing fields

Valid

7. Contact Numbers incorrectly

filled

Show error, please

enter proper contact

numbers

Valid

8. Check is removed from the terms

and conditions

Show error, please

check the terms and

conditions to proceed

Valid




Institute Registration Module:


1. All inputs are valid Redirect to Institute

username and

password page.

Valid

2. Registration number and license

number incorrectly filled.

Does not allow to store

the details

Valid

3. First Name/ Last Name not filled

or incorrectly filled

On next tab show error

message, Enter first

name and Last name

Valid

4. Email Address not in proper

format

Show error in the next

tab, Enter valid email

address

Valid


not long enough

Valid


dont match

Valid

7. Address fields missed Show error, please fill

missing fields

Valid

8. Contact Person name incorrectly

filled

Show error, please

enter proper contact

Person name.

Valid




Doctor Registration Module:


1. All inputs are valid Redirect to Doctor

username and

password page.

Valid

2. Registration Date incorrectly

filled.

Does not allow to store

the details

Valid

3. Username incorrectly filled Does not allow to store

the details as first 4

characters should be

alphabet.

Valid


not long enough

Valid


dont match

Valid


chapter 7 testing

Documents