TOWARDS SOFTWARE The Dictionary for

TESTING
Software Testers

The Importance of Software Testing in the current IT Industry and the

procedure followed to attain the Bug free application/Product
About the Author

In his words

Dedicating my hard work and this book to.

Almighty God and my Beloved Parents

**********************************************************************************
Praveen has been a B Tech Graduate in Computer science and Information Technology from GATES
INSTITUTE OF TECHNOLOGY, GOOTY (2005) affiliated to JNTU. He Mastered the Testing concepts soon
after finishing his graduation and worked as trainer for students in CMC (Hyderabad).

He later joined as Software Tester in Global Exchange Services (Bangalore) in 2007 and continued his
research as quality expert in various domains and projects, driving the quality with the aim of zero defect
product and certainly achieved it in B2B domain. He also worked with various teams in promoting the
quality principles to make software testing easy to understand and perform its execution.

Achieved Thank you Awards and Night on Town Awards on various occasions for his hard work and
efficiency. He also worked in automating the testing tasks using various tools like, Win runner, QTP,
Rational Robot, etc. Created an outstanding test plan document and implemented performance testing
using various tools like JMETER, LOAD RUNNER. Currently working with Computer Associates
(Bangalore) on Network Analytics domain and doing research on developing a new life cycle model for
Testing in order to achieve the Bug free application

PRAVEEN KUMAR

**************************************************************************
1. INTRODUCTION ----------------------------------------------------------------(1)
2. Software Development life Cycle--------------------------------------(2)
3. Life Cycle Models--------------------------------------------------------------
4. STLC
5. Test Plan and its stages
6. Test Case Types
7. Testing Methodologies
8. Test Types
9. Bug Life Cycle
10. Quality Control and standards
11. Manual testing vs Automation
12. Automation Types & Overview
13. Estimations for Testing in IT Industry
14. Manual Interview Questions
15. Questionaire
SDLC(Software Development Life Cycle):
Currently in the IT Industry, many applications and softwares are being developed with a basis of
information and with certain process.
Specifically in order to develop the software/Application, we need to follow the models defined by the
IEEE standards.

The SDLC schematic diagram is as below

Feasibility Analysis:
This is the first and basic stage to work/develop the software application. In this Stage,
the marketing personal/ Management people will try to collect the basic information required to
start/develop the application. Basic information like as follows

a) Technical Feasibility(s/w, h/w, machinery,etc)

b) Schedule Feasibility(Time will be estimated roughly for completion)
c) Financial Feasibility( Rough sketch on amount of money to be quoted will be estimated here)

Requirements Collection:
Here in this stage mostly the Business Analyst/Senior Developer/Senior tester will
involve to get the information of actual requirements needed to develop the software.
As part of the Requirements collection, the company will go to the customer for their feedback on the
application and the information required to develop it..
Based on the feedback, we will get to collect the following information as part of requirements

a) User Interface: As part of the user interface, we will collect the feedback from client about the
screens, frames, font, size, text, enable, disable, fields on the web page, active Inactive, colour, etc.
b) Functional Requirements: As part of this functional requirement collection, we will collect the
information about the number of buttons required in the page , page navigation from one page to
another page, etc.
c) Performance requirements: As part of this performance requirements, we will collect the
information about the response time when we send a request to the server and the application
behavior (Example like if a=1, b=2 ,c=a+b. In this case how much time will system takes to execute
a+b for first time and how time will it take to execute a+b for the second time)
d) Environment Requirements: As part of this environmental requirements, we will collect the
complete information about the operating systems(WINDOWS/LINUX/UNIX/etc), Hardware(RAM,
others, etc)
e) Standards: As part of the Standards, we will collect the information about the IEEE standards that
we have to use in order to develop the products related to standards like ISO, British standards, etc.

Once the requirements are collected completely, then all the information will be documented and that
document will be sent to client for his review over the requirements.

We can classify the requirements in the form of documents here as below

BRS (Business Requirements Specification Document): BRS will deal all high level information such as
security related information like Authentication, Authorization.

SRS (System/Software requirements Specification document): This Document deals about the complete
requirements collected (Functional +Non Functional) information. This SRS will be given to the client for
the reference. But client will face difficulty in understanding the technical information given in the SRS.
So in order to avoid the confusion to the client, we will incorporate the Functional information in a
separate document called as FRS.
FRS (Functional Requirements Specification Document): This Document generally contains all the
functional related information of the project. FRS will be usually given to the Testing
Team/Development Team.

Design:
The most important aspect for developing the application is the design. The design is more like
drawing the picture of the house before constructing it.The design has of three types
UI Design: As part of the UI design , we will develop the front end screens, frames in the web page,
colour, size, font, active, inactive, enable, disable, etc .In order to develop this , we can either have the UI
specialist to design or the developers can do the same

Application Design: As part of the application design, we normally define the strategy and the way to
write the code for the application.