See discussions, stats, and author profiles for this publication at: https://www.researchgate.

net/publication/330280159

SOFTWARE TESTING REQUEST, TEST CASES AND REPORT DOCUMENTATION

FOR COMPLETENESS, CORRECTNESS AND RELIABILITY: A CASE STUDY

Conference Paper · January 2019

CITATIONS READS

0 1,664

2 authors:

Ajay Kumar Seema Bawa

Chitkara University Thapar Institute of Engineering and Technology
26 PUBLICATIONS   77 CITATIONS    144 PUBLICATIONS   1,050 CITATIONS   

SEE PROFILE SEE PROFILE

Some of the authors of this publication are also working on these related projects:

Framework for Efficient Query processing in Wireless Sensor Networks View project

Special Manpower Development Project for VLSI and related software (SMDP-VLSI) Phase - II View project

All content following this page was uploaded by Ajay Kumar on 12 June 2021.

The user has requested enhancement of the downloaded file.

 SOFTWARE TESTING REQUEST, TEST CASES AND REPORT
DOCUMENTATION FOR COMPLETENESS, CORRECTNESS AND
RELIABILITY: A CASE STUDY.
Ajay Kumar
Asst Professor, CSIT,
Mewar University, Chittorgarh, Rajasthan (India)
[email protected]

Seema Bawa
Professor and Dean, CSED,
Thapar University, Patiala, Punjab (India)
[email protected]
ABSTRACT
The increasing visibility of software as a system element and associated with a software
failure are the attendant costs a, planned thorough testing. It is not renovating forces for
a software development organization to unusual for software project effort on testing[4].
In the extreme, testing of human-rated software can cost three to five times as much as all
other software engineering activities combined. Quality assurance is the review of
software products and related documentation for completeness, correctness, reliability
and maintainability. It also includes assurance, that the system meets the specification
and the requirements for its intended use and performance. In this research paper, I
present an overview of our experience through a case study and also provide some new
techniques. Using new techniques SQA team can easily construct a proper documentation
of complete test report.

Keywords: Software Testing, Documentation, Test-cases, Test Report, Error Severity

General Terms: SQA-Software Quality Assurance, TC-Test Case, UT-Unit Testing.

INTRODUCTION

Software testing is critical element of software quality assurance and represents the ultimate review of
specification, design and coding. The main objectives of software testing are: - 1) exercising a program
with the intent of finding the errors, 2) A good test case is one that has a high probability of finding the
undiscovered error; 3) A successful test is one that uncovers all the undiscovered errors. If the software
testing is completed successfully (according to the objectives), then it will uncover errors in the software.
As a secondary benefit, testing demonstrates that software functions appear to be working according to
specification, that behavioral and performance requirements appear to have been met [1][5][6]. In addition,
data collected as testing is conducted provide a good indication of software reliability and some indication
of software quality as a whole. But testing cannot show the absence of errors and defects, it can show only
that software errors and defects are present. It is important to keep this statement in mind as testing is being
conducted and must be construct proper documentation of complete software testing report. Writing an
effective status report is as important as the actual work I have done. The main problem arise how to write
an effective status report of our complete testing process? How to write effective Test cases, procedures
and definitions[3][7]? Test report is important to track the important project issues, accomplishments of the
projects, pending work and milestone analysis. Even using these reports we can track the team performance
to some extent [2]. From this report prepare future actionable items according to the priorities and make the
list of next time actionable. Here we are going to give some templates and techniques to construct
appropriate documentation and also we implement these templates and techniques with the help of a case
study on Gas Agency Operations (GAOs).
CASE-STUDY: SATYAM GAS AGENCY OPERATIONS

Satyam Gas Agency provides facility to public. It provides services of LPG that is cooking gas. Satyam
Gas Agency provides gas connection with regulator, stove and pipe. Satyam Gas Agency has a large
collection of consumers who take gas and turn with services. The agency provides many facilities for
consumers like new gas connection, gas refilling, and gas cylinders delivery; apply some offers time-to-
time etc. It makes the faster working and good customers services. It reduces the processing time for
customer queries and organizational queries. Implement more security and protection mechanism and ease
of maintenance.

SOFTWARE TEST REQUEST TEMPLATE

Testing Request

1 Client (Project) Name SATYAM GAS AGENCY Ltd.

2 Application Name GAS AGENCY OPERATIONS (GAOs)

3 Current Version 1.0

4 Previous Version NA
Status of previous Version (PI/ Prod Test/ Prod/ Prod with
5 Sign Off) NA
Previous version Sign-Off date (if sign-off has been
6 received) NA
7 Received Date of ARF / Requirement
8 Accepted ARF sending back date
9 Expected Release Date
10 Committed Release Date
11 Committed Release Date for Internal Testing
12 Released during First Half OR Second Half (Cut off time)
13 Smoke Testing Done? Yes/No Yes
14 Unit Testing Done? Yes/No Yes
15 Unit Test Case Template Attached? Yes/No Yes
16 Application Folder Path D:\gao.exe
17 VSS Path
18 Release Deliverables / Attachments
19 List of People to make Release to
20 Release Location Thapar University, Patiala
Ajay Kumar, Sanjay Kumar, Ashok
21 Point Person (Development) and Naveen.
22 Any Open Issue(s)

Note: If any of the above field is incorrect, you need to resend the testing request

The main objectives of this project are to automate all the activities that place in any Gas Agency. At this
time these activities are done manually. Now management wants to all activities performed by computer.
There are following scopes of this project:
• The application is designed to increase the efficiency of agency users.
• All data processing and storage will be done in grid computing [5] environment.
 • Save lot of time because it will eliminate the manual effects required saving and retrieving data
into Cloud Database [4].
• The system should provide a login mechanism for the administrator, some employees.
• Only administrator of the system should be able to enter user or modify any kind of information in
the system, but every employee of agency with a valid login ID and password should be able to
view all the details.
• Online view/printing of reports.
• A generic development framework.
• A centralized database.
• Automatic reduction of stocks with generation of reports.

TEST CASES

Test cases are most important document for every software SQA team or software tester. Our GAOs
application consist number of modules/forms. These modules are: Validation form, Add new customer,
Order booking, Order processing, Employee Details etc. Here I describe how to generate test cases and
document of above modules[3].

Test cases for Validation to be perform (login form)

• The users enter user id and password in the appropriate text box.
• If number of attempts is less than 3, allow a user to re-enter the user name and password,
otherwise, terminate the application.
Sources of input:
Login Form
Inputs:
Input Unit of Measure Validation rules
User ID Character Exactly 10 characters
e.g. CG00000112
start with CG
Password Character >=6 and <=15
alphanumeric
Process:
Operations Validity Check on Input Intermediate Data produced
Capturing/Records User ID and Password are Login Record
from textboxes matched, No filed is left blank
Output:
Open main screen and appropriate options and menus.

Test cases for Add New Connection (Customer form)

This form provides Add new gas connection for new customer. Customers have to fill the appropriate form
and give some address proof such as Driving License, Photo ID etc.
Sources of input:
New Connection Form
Inputs:
Input Unit of Measure Validation rules
Customer name Character <=15 characters
Address Character <= 40 characters
Phone No Character <=10 characters
 Connection Type Character <=15 characters
Process:
Operations Validity Check on Input Intermediate Data
produced
Capturing/Record No any filed is left blank Connection ID and
input in the textboxes Connection date

Output:
Computer operator has to submit all the appropriate details of customer and system generates a
unique connection_id.

Test cases for Order booking details

Customer can give the order for booking new gas cylinder by phone no or directly go to agency. In this
movement customer have to produce connection no., address and their needs such as, no of cylinders,
stoves, regulator etc.
Sources of input:
Order Booking
Form
Inputs:
Input Unit of Measure Validation rules
Connection_ id Character 10 Characters
Date Date DD/MM/YY
No of cylinder Integer 1 to 1000
Process:
Operations that need to be performed on Input Data
Operations Validity Check on Input Intermediate Data produced
Capturing/Records Connection no must be correct Customer details and stock details
from textboxes and check in customer details databases.
database.
Output:
After booking order system generates a booking no. with appropriate date and sent this
information to order delivery.
Test cases for Order delivery
Agency deliver appropriate no of cylinder on particular customer’s address by own employee. And
generate reports for customer copy and agency copy. If delivery is successful then delete the booking order
details of particular customer.
Sources of Input:
Order Delivery Form
Inputs:
Input Unit of Measure Valid Range
Connection_id Character 10 Characters
Customer name Character 20
Amount Money Manually entered in
rupees (Rs.)
Date Date DD/MM/YY
No of cylinder Integer Positive Integer
(>=0 and <=1000)
Process:
Operations that need to be performed on Input Data
Operations Validity Check on Input Intermediate Data produced
Capturing/Record Connection no must be correct Order booking details,
input in the textboxes and check in order booking Customer details and stock
details, customer details and details.
 stock details databases.
Output:
Here system generates two reports one for customer copy and second for agency. This report must
consist the customer name, customer address, connection_id, delivery date, and amount.

PERFORMANCE TESTING

Generally the testing can be widely classified into two categories: 1) knowing the internal working of a
product, test can be conducted to ensure that “all the gears mesh”, that is the internal operation of the
product performs accordingly to specification and all internal components have been adequately exercise.
2) Knowing the specified function that a product has been designed to perform, test can be conducted that
demonstrate each function is fully operational.
Test cases for Performance testing
Here we consider both the static and the dynamic numerical requirements testing placed on the software or
on human interaction with the software as a whole.
Static numerical requirements testing
Following table indicates the static numerical requirements:
1 The no of terminals to be supported <=10 machines

2 The no of simultaneous users to be supported <=10 user(s)

3 Amount and type of information to be handled 10 kb/sec for text data

20 kb/sec for graphical data
Dynamic numerical requirements testing
Dynamic numerical requirements include, our total no of tasks such as add new connection, report
generation and the amount of data to be processed within certain time periods for both normal and peak
workload conditions.
Here we measure each task would be processed in less than 1 sec. It means 100% task performed
in less than 1 sec.

TEST CASE DESCRIPTION AND REPORT

Following table depicts the complete description of test cases. It describes how describe a complete test
cases and how can document the test results. Second table exhibits the final report with the errors severities.

TEST CASE DESCRIPTION

Version 1.0.0
DATE:12 JAN 2012
NAME OF DEVELOPER: AJAY KUMAR
APPLICATION NAME: GAOs
NAME OF CLIENT: SATYAM GAS AGENCY LTD.
S. UNIT Test Test case Instruction/ Pre- Input value Expected Result Actual
NO SECTION Case ID condition Result
1 Textbox (left TC1 All mandatory fields should Name,Address,Age, All value should be PASS
blank or not) not be left blank Phone no appropriate range
and type
2 Navigation TC2 Direct navigation points Move first, move last, All button should PASS
buttons move next, move prev. work appropriate
functions
3 Record TC3 Database work properly and Add new, save, delete, All records PASS
Operations all table should be created modify, cancel records operations work
buttons properly with
appropriate
database
 4 Combo box TC4 Select only one item at same Department ID, User Select appropriate PASS
(select or time name value
unselect)
5 Label (visibility) TC5 Appropriate format Specify to all the fields Display in proper NOT
formatting PASS
6 Frame (group or TC6 Grouped all options buttons Search by code, search We select only one PASS
ungroup) by phone option button in
same group
7 Form (load of TC7 Like a container, contain all Establish connection Load and unload NOT
Unload) the controls with database properly PASS
8 Status bar TC8 Date and time in bottom right Not Applicable Display date and NOT
corner Time PASS
Note: - ALL THE TEST CASES ENSURES THAT REQUIREMENTS ARE COVERED COMPLETELY.

TEST CASE REPORT

Version 1.0.0
NAME OF TEST ENGINEER: AJAY KUMAR

Start Date Jan 02, 2012

End Date Jan 12, 2012
Test Cases ID TC1 TC2 TC3 TC4 TC5 TC6 TC7 TC8 TOTAL

Major Y
SEVERITY
Medium

Minor

Fail Test Cases ID

Pass Test Cases ID

Total Test Cases

REMARKS

CONCLUSION
Test cases are important document for future prospective. Quality assurance team is the review of software
products and related documentation for completeness, correctness, reliability and maintainability. It also
includes assurance, that the system meets the specification and the requirements for its intended use and
performance. In this research paper, I present an overview of our experience through a case study and also
provide some new techniques. Today, most of the programmer/test engineers have face many problems
regarding test case documentation.

REFERENCES

[1] Pressman R. S, “Software Engineering: A Practitioner’s Approach”, Sixth edition, 2010, McGraw Hill.
[2] Pankaj Jalote, “An Integrated Approach of Software Engineering”, Springer Verley, 2 nd edition, 1994.
 [3] Combining software testing strategies: an empirical evaluation”, IEEE workshops on software testing,
36(11): 82-90 July 1986.
[4] Ahuja, A., Kumar, A., & Singh, R. (2012). An approach for virtualization and integration of
heterogeneous cloud databases. International Journal of Engineering Research and Applications, 2(5), 352-
355.
[5] Kumar, Ajay, Seema Bawa, and Vishnu Sharma. "Dynamic and Scalable Data Storage Management in
Grid environments." National Conference on Emerging trend in Engineering and Sciences at Samrat Ashok
Technological Institute,(MP), India. 2010.
[6] Web ref please see: http://www.stcthirdeye.com/request-proposal.htm
[7] Web ref please see: http://www.softwaretestinghelp.com/web-testing-example-test-cases/
[8] Web Ref please see: http://www.softwaretestinghelp.com/tips-to-design-test-data-before-executing-
your-test-cases/
[9] H. S. Nagalakshmi, Lakshmi Dixit, “Software Engineering Evaluation and Testing”, NCSEPP-2004, pg.
44-47.

About Authors

Ajay Kumar has received BCA/MCA and M. E. (SE) degrees from IGNOU New
Delhi and Thapar University Patiala respectively. Currently he is working as an
assistant professor at CSE department, Mewar University, Chittorgarh and
pursuing Ph. D. program from Thapar University also. His areas of interests
include Grid Computing, Software Engineering, Web services and Network
Security. His current research focus on large-scale data management in Cloud
Computing environments. In addition to his contribution to C# .Net Developer on
various domains also published many research papers.

Dr. Seema Bawa, an alumni of IIT Kanpur, IIT Kharagpur and Thapar University
has demonstrated her intellectual, interpersonal and managerial skills in various
domains. Having vast industrial experience of working in IT industry with the role
of Project Leader and Project Manager, currently she is a Professor of Computer
Science and Engineering and Head of Centre for Information Super Highway at
Thapar University, Patiala. Her areas of interests include Parallel and Distributed
Computing, Grid Computing, VLSI Testing and Network Management. Her
current research focus is on Cloud Computing and Cultural Computing. Along
with being a committed teacher and a passionate researcher, she has been actively
contributing her services for underprivileged sections of the society.

View publication stats