White box testing is based on the structure of software and is used mainly at the unit testing phase.
The following are recognised white box test design and measurement techniques;
 Statement testing
 Branch / decision testing
 Data flow testing
 Branch condition testing
 Branch condition combination testing
 Modified condition decision testing
 LCSAJ testing
Black Box Testing
Black box testing is used to test the behaviour or functionality of the system, with no regard to its internal software structure. It is appropriate during all test phases, but is prevalent during the later phases (system test and UAT).
The following are recognised black box test design and measurement techniques;
 Equivalence partitioning (EP); dividing the test inputs and outputs into
equal areas, on the assumption that if one value works, all will work, and that
one value from each partition gives better test coverage than all from one.
 Boundary value analysis (BVA); this technique assumes that faults tend to
be found near input/output boundaries and that testing should be concentrated
immediately either side of boundaries.
 State Transition Testing; this uses a model that shows all states the software
may occupy, the transitions between the states, events which cause the
transitions and actions arising from the transitions. Tests are therefore
designed to exercise the transitions between states.
NONE OF THEM help a business analyst in requirements gathering!
Main Topics
Browse All Topics
by: SunBowPosted on 2005-02-22 at 08:29:05ID: 13372940
http://www.webopedia.com/T
Also known as glass box, structural, clear box and open box testing. A software testing technique whereby explicit knowledge of the internal workings of the item being tested are used to select the test data. Unlike black box testing, white box testing uses specific knowledge of programming code to examine outputs. The test is accurate only if the tester knows what the program is supposed to do. He or she can then see if the program diverges from its intended goal. White box testing does not account for errors caused by omission, and all visible code must also be readable.
http://www.ddj.com/article
Traditionally, there are two main approaches to testing software: "black-box" (or functional) testing, and "white-box" (or structural) testing. White-box testing strategies include designing tests such that every source line of code is executed at least once, or requiring every function to be individually tested.
http://www.faqs.org/faqs/s
Black-box test design
treats the system as a "black-box", so it doesn't explicitly use
knowledge of the internal structure. Black-box test design is usually
described as focusing on testing functional requirements. Synonyms for
black-box include: behavioral, functional, opaque-box, and
closed-box. White-box test design allows one to peek inside the "box",
and it focuses specifically on using internal knowledge of the software
to guide the selection of test data. Synonyms for white-box include:
structural, glass-box and clear-box.