Scribd
Upload
19 views

Software Testing - Overview

ST

Uploaded by

John Gablac
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
19 views

Software Testing - Overview

ST

Uploaded by

John Gablac
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Page 1 of 3

Software Testing - Overview


What is Testing?
Testing is the process of evaluating a system or its component(s) with the intent to find
whether it satisfies the specified requirements or not. In simple words, testing is executing
a system in order to identify any gaps, errors, or missing requirements in contrary to the
actual requirements.

According to ANSI/IEEE 1059 standard, Testing can be defined as - A process of analyzing


a software item to detect the differences between existing and required conditions (that is
defects/errors/bugs) and to evaluate the features of the software item.

Who does Testing?


It depends on the process and the associated stakeholders of the project(s). In the IT
industry, large companies have a team with responsibilities to evaluate the developed
software in context of the given requirements. Moreover, developers also conduct testing
which is called Unit Testing. In most cases, the following professionals are involved in
testing a system within their respective capacities −

Software Tester
Software Developer

Project Lead/Manager

End User

Different companies have different designations for people who test the software on the
basis of their experience and knowledge such as Software Tester, Software Quality
Assurance Engineer, QA Analyst, etc.

It is not possible to test the software at any time during its cycle. The next two sections
state when testing should be started and when to end it during the SDLC.

Explore our latest online courses and learn new skills at your own pace. Enroll and
become a certified expert to boost your career.

When to Start Testing?


An early start to testing reduces the cost and time to rework and produce error-free
software that is delivered to the client. However in Software Development Life Cycle
(SDLC), testing can be started from the Requirements Gathering phase and continued till
the deployment of the software.
Page 2 of 3

It also depends on the development model that is being used. For example, in the
Waterfall model, formal testing is conducted in the testing phase; but in the incremental
model, testing is performed at the end of every increment/iteration and the whole
application is tested at the end.

Testing is done in different forms at every phase of SDLC −

During the requirement gathering phase, the analysis and verification of


requirements are also considered as testing.

Reviewing the design in the design phase with the intent to improve the design is
also considered as testing.

Testing performed by a developer on completion of the code is also categorized as


testing.

When to Stop Testing?


It is difficult to determine when to stop testing, as testing is a never-ending process and
no one can claim that a software is 100% tested. The following aspects are to be
considered for stopping the testing process −

Testing Deadlines

Completion of test case execution

Completion of functional and code coverage to a certain point

Bug rate falls below a certain level and no high-priority bugs are identified

Management decision

Verification & Validation


These two terms are very confusing for most people, who use them interchangeably. The
following table highlights the differences between verification and validation.

Sr.No. Verification Validation

Verification addresses the concern: "Are Validation addresses the concern:


1
you building it right?" "Are you building the right thing?"

Ensures that the software system meets Ensures that the functionalities
2
all the functionality. meet the intended behavior.

Verification takes place first and includes Validation occurs after verification
3 the checking for documentation, code, and mainly involves the checking of
etc. the overall product.
Page 3 of 3

4 Done by developers. Done by testers.

It has static activities, as it includes It has dynamic activities, as it


5 collecting reviews, walkthroughs, and includes executing the software
inspections to verify a software. against the requirements.

It is an objective process and no It is a subjective process and


6 subjective decision should be needed to involves subjective decisions on
verify a software. how well a software works.

You might also like