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
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.
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. 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.
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
These
two terms are very confusing for most people, who use them interchangeably. The
following table highlights the differences between verification and validation.
How to learn software
testing?
Learn
IT Training is a comprehensive repository for online and offline courses
offering high quality state-of-the-art IT and Business related e-learning
trainings and courses apart from SAP training modules. It is one of the best global online training portals for
the students. We provide trainings throughout USA, UK,
Australia, UAE, Canada, Saudi Arabia, New Zealand, India and Many other
Countries with industry experts.
Want
to join with us to establish a testing career, Take a free demo today CLICK HERE
For more details contact us:
VISIT: www.learnittraining.com
INDIA: +91 9912989639
USA: +12108585008
Contact@learnittraining.com
Skype:Learn IT Training
WhatsApp: +91 9912989639
No comments:
Post a Comment