Black-Box , White-Box Testing
I want to know the exact functionality of
these testing . What should i test using these
testing methods.Pls. clarify
Re: Black-Box , White-Box Testing
In Brief -
For white Box:
this means test the software code. for e.g if you are testing a Loop in a function then test each and evry step, I mean execute atleast once each & every loop path to ensure that code is working properly.
For black box:
As it is a black box teting you have to check the functionality according to the specs and the business logic.
You have to check that proper output is achieved if you enter a input data.
You can also search for "White Box Testing" & "Black Box testing" on this forum to get more details.
Re: Black-Box , White-Box Testing
I have found a concrete definition for the white box and the black box testing. I am pasting that here for your reference.
White box testing
Structural tests verify the structure of the software itself and require complete access to the object's source code. This is known as ‘white box’ testing because you see into the internal workings of the code.
White-box tests make sure that the software structure itself contributes to proper and efficient program execution. Complicated loop structures, common data areas, 100,000 lines of spaghetti code and nests of ifs are evil. Well-designed control structures, sub-routines and reusable modular programs are good.
Many studies show that the single most effective defect reduction process is the classic structural test - the code inspection or walk-through. Code inspection is like proofreading - it can find the mistakes the author missed - the "typo's" and logic errors that even the best programmers can produce. Debuggers are typical white-box tools.
White-box testing's strength is also its weakness. The code needs to be examined – by highly skilled technicians. That means that tools and skills are highly specialized to the particular language and environment. Also, large or distributed system execution goes beyond one program, so a correct procedure might call another program that provides bad data. In large systems, it is the execution path as defined by the program calls, their input and output and the structure of common files that is important. This gets into a hybrid kind of testing that is often employed in intermediate or integration stages of testing.
Black Box Testing
Functional tests examine the observable behavior of software as evidenced by its outputs without reference to internal functions. Hence ‘black box’ testing. If the program consistently provides the desired features with acceptable performance, then specific source code features are irrelevant. It's a pragmatic and down-to-earth assessment of software.
Black box tests better address the modern programming paradigm. As object-oriented programming, automatic code generation and code re-use becomes more prevalent, analysis of source code itself becomes less important and functional tests become more important.
Black box tests also better attack the quality target. Since only the people paying for an application can determine if it meets their needs, it is an advantage to create the quality criteria from this point of view from the beginning.
Black box tests have a basis in the scientific method. Like the process of science, functional tests must have a hypothesis (your specifications ), a defined method or procedure (your test), reproducible components (your test data), and a standard notation to record the results.
You can re-run black box tests after a change to make sure the change only produced intended results with no inadvertent effects.