Home

Search

Guestbook

Contact Us

Log in

Join Us

Testers Community

Link to Us

Advertise with Us

 
 

This Newsletter Brought to You by

The leading web-based task and bug tracking software for software development and IT! More...

 
 

Promote Your Products and Services

SQAtester.com Storefront Program is the best way to help companies promote their products and services.
More...


 
 

Find out which Bug-Track.com account is right for your software development team, Try our Demo Now!

 
 

Access to your Information Quickly and without hassle.

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

Try Software Planner FREE for 2 weeks

 
  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...
 
 

You are here: Home > Testing Newsletter > Testing Newsletter June 2005

Try Bug-Track.com Now!
Web-based bug and project management tool for SQA Tester Visitors.

SQAtester.com monthly newsletter reaches its receptive audience directly through. Advertisers can place their message with a link or banner to their site.
What is "White Box" Testing? ____________________________
shared by Mikhail Rakhunov

White box testing is usually contrasted with black box testing, which is testing only via established, public interfaces such as the UI or the published API. Glass box and transparent box are synonyms for white box.

The simple answer is white box testing is testing that is done with knowledge of the internals of the product. This boils down to several activities. Code coverage, mutation testing, unit and/or component testing, fault insertion, etc.

Code coverage is a way of measuring your tests. You determine which lines/branches/procedures have been executed during your test runs and continue developing tests until you hit some target percentage.

Mutation testing is another way of measuring your tests. You insert a bug on purpose into the product and run your tests. At least one (preferably exactly one) test should fail.

Component or unit testing involves removing a block of code from the product, writing a driver to sit over it and stubs to sit under it and testing the code standalone.

Fault Insertion involves forcing return codes to indicate errors and seeing what happens. This is a good way to simulate certain events, such as disk full, out of memory, etc.

I think of glass box testing as part of the programming process because so many programmers routinely ran white (glass) box tests of their modules just before and just after integrating them with other parts of the system
Share the Experience and Exchange Ideas in SQAtester Group.

E-mail to a Friend.
We at SQAtester.com, look forward to building a lasting, creative, and friendly relationship with our community. Good luck, and happy
Joining!
 

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...
 

 

 

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