Home

Search

Guestbook

Contact Us

Log in

Join Us

Testers Community

Link to Us

Advertise with Us

 
 

See Also

Best Practices for Software Projects - Risk Management. More...

Best Practices for Software Projects - Estimating.
More...

Minimizing Software Defects via Inspections. More...

Testing GUI. More...

Best Practices for Software Projects - Software Measurements. More...

Test Reviews. More...

Key QA Documents. More...

Improving the Quality process by doing the
Metrics Calculation

Download

Zero-Defect Software Development.
More...

 
 

Promote Your Products or Services

Interested in promoting your products on SQAtester.com?
If so, we think you'll like
our
Product Storefront Program.
The concept is simple.

More...


 
 

FREE Try our [ASP Hosted solution] for free for one month, no obligation to pay.
An extremely practical and cost effective Web Based Bug Tracking Software and help desk software ready to be integrated into company intranet today.
More...

 
 

Learn more material at a Fraction of Price!

Get the training that will help you face the challenges and meet the demands of today's competitive market place.
Programs Offered: Oracle DBA, Cisco Networking, Software Testing & Programming. More...

 
 

To compete in today's market, you need Access to your Information Quickly and without hassle.
We can make this possible.

FREE 2 week trial

 
 

Maximum Performance and Reliability.

Try our bug tracking system. We would also appreciate your feedback and comments. More...

 
 

You are here: Home > Methodology and Techniques > What is Gray Box Testing

 
What is Gray Box Testing _______________________________
Question:
What is Gray Box Testing? Where & how Gray Testing is used?

Posted by ashu_akl

Answer:
Let's begin with the most basic
forms of testing: white box, or glass box
versus black box testing: I will quote from
Testing Computer Software:
Second Edition (1993) Cem Kaner, Jack Falk, Hung Quoc Nguyen.

Glass box testing is distinguished from black box testing, in which the program is treated as a black box. You can't see into it. The tester (or programmer) feeds it input data, observes output data, but does not know, or pretends not to know, how the program works. The test designer looks for interesting input data and conditions that might lead to interesting outputs. Input data are "interesting" representatives of a class of possible inputs if they are the ones most likely to expose an error in the program.

In contrast, in glass box testing, the programmer uses her understanding and access to the source code to develop test cases.

At this point, on page 41of
Testing Computer Software, they go into explaining the benefits of white box testing. They also spend the next few pages going over the concepts of white box testing.

In recent years I have also heard of gray box testing. In this form of testing, the tester has access to some of the inner workings of the system, usually the database, but not the code.

White box testers have access to the code, but even a black box tester canknow the branches of code--the rules within the code that cause operations to fork. A white box tester generally uses the code, and the ability to create drivers and stubs to test the code directly. They do not rely on the UI to do it.

The typical gray box tester is permitted to set up his testing environment,
like seeding a database, and can view the state of the product after their
actions, like performing a SQL query on the database to be certain of the
values of columns. It is used almost exclusively of client-server testers or
others who use a database as a repository of information, but can also apply to a tester who has to manipulate XML files (DTD or an actual XML file) orconfiguration files directly.

The true black box tester looks only at the GUI and can not touch intermediate files, registry entries, databases, etc., nor are they permitted to see the results their actions have wrought, other than through the UI. They are, therefore, only permitted to use the UI to do their testing.

Posted by Walter Görlitz
Share your thoughts on What is Gray Box Testing in SQAtester Group.

E-mail to a Friend.
 

Top

Books to Read ________________________________________
 
 

Testing Computer Software, 2nd Edition
The original printing of Testing Computer Software set the standard for the emerging field of test engineering with a full tour of the state of the art in managing the testing process. The reissued text makes this classic out-of-print text available once again. Though it relies heavily on older.
More...
 

 
 

Automated Software Testing
Written for those with some background in software engineering, Automated Software Testing: Introduction, Management, and Performance delivers a rigorous guide to the state of the art in managing automated testing in a text that will benefit anyone who tests software for a living.
More...
 

More... books on Software Testing.
 

Top

Categories ________________________________
Bugs and Fixes   Software Life Cycle  
Bugs Life   SQA Career  
Bug Tracking   Testers Area  
Companies and Products   Tester toTester  
Documentation and Strategy   Testing Center  
Methodology and Techniques   Testing Newsletter  
More Resources   Testing Tips  
Publication and News   Tools and Automation  
QATeam   Tutorials and Training  
Community ________________________________
Join Now Free   Message Forum  
Share Your Experience   Professional Profiles  
Specials __________________________________
Millions of titles discounted up to 40-90% off. Great low prices on your favorite books. More...   Find all of your favorite software.
More...
 

 

One of the most important (and most common) things an SQA Engineer does is to write "bug reports". How well you report a bug directly affects how likely the programmer is to fix it. More...

 

© Copyright since 2000 by SQAtester.com. All Rights Reserved. For information on SQAtester.com, visit About Us