I'm trying to understand one in terms of how it compares to the other.
Is white box testing where you can see the code and black box testing where you don't look at the code?
Q) Is white box testing where you can see the code and black box testing where you don't look at the code?
It is a process of giving the input to the system and checking the output of the system, without bothering about the system that how the system generates the output. It is also call as behavior testing, data-driven testing or I/O driven testing, functional testing .
testing based solely on analysis of requirements (specification, user documentation etc)
Advantages:
1) More effective on larger units of code than glass-box testing.
2) Tester and Programmer are independent of each other.
3) Tests done according to users point of view.
4) test-cases can be designed as soon as specifications are complete.
Disadvantages:
1) It may leave many program path untested.
2) Only small number of possible inputs can actually be tested, to test every possible. input stream would take nearly forever.
It is a process of giving input to thee system and checking that how the system processes the input to generate the output.
It is mandatory for tester to have the knowledge of the code.
Advantage:
1) This type of testing helps to uncover defects at structural level. The tests go below the top and functional layer to uncover the defects
Disadvantages:
1) Does not ensure the user requirements are met
2) Does not establish if the decisions, condition ans paths.