Gray-box testing
(International English spelling: grey-box testing) is a combination of
white-box testing and black-box testing. The aim of this testing is to search
for the defects if any due to improper structure or improper usage of
applications. Gray-box testing is also known as translucent testing.
A black-box tester is
unaware of the internal structure of the application to be tested, while a
white-box tester knows the internal structure of the application. A gray-box
tester partially knows the internal structure, which includes the access to
internal structures as well as the algorithms for defining the test cases.
Gray-box testers require
overall and detailed description of documents with required documents of the
application. Gray Box Testing collects the information for defining testcases.
Gray-box testing is
beneficial because it takes the straightforward technique of black-box testing
and combines it with the code targeted systems in white-box testing.[5]
Gray-box testing is
based on requirement test case generation because it presets all the condition
before program is tested by using assertion method. Requirement specification
language is used to state the requirements which make easy to understand the
requirements and verify its correctness too where input for requirement test
case generation is the predicates and the verification discussed in requirement
specification language.
EXAMPLE
For example, consider a
hypothetical case wherein you have to test a web application. Functionality of
this web application is very simple, you just need to enter your personal
details like email and field of interest on the web form and submit this form.
Server will get this details, and based on the field of interest pick some
articles and mail it to the given email. Email validation is happening at the client
side using Java Scripts.
In this case, in the
absence of implementation detail, you might test web form with valid/invalid
mail IDs and different field of interests to make sure that functionality is
intact.
But, if you know the
implementation detail, you know that system is making following assumptions
·
Server
will never get invalid mail ID
·
Server
will never send mail to invalid ID
·
Server
will never receive failure notification for this mail.
So as part of gray box
testing, in the above example you will have a test case on clients where Java
Scripts are disabled. It could happen due to any reason and if it happens,
validation can not happen at the client site. In this case, assumptions made by
the system are violated and
·
Server
will get invalid mail ID
·
Server
will send mail to invalid mail ID
·
Server
will receive failure notification.
Er Ratnesh Porwal
Software Engineer
www.AeroSoftCorp.com
www.AeroSoft.in
www.AeroSoft.co.in
www.AeroSoftseo.com
On Line Assistence :
Gtalk : ratnesh.aerosoft@gmail.com
Y! Messenger : ratnesh.AeroSoft@yahoo.com
Rediff Bol ratnesh.AeroSoft@rediffmail.
AeroJobMark , Best Pilot Jobs ,Airplane,Aviation, jobs, Airline, Pilot, employment
No comments:
Post a Comment