I don't think that's an either...or... question. In my opinion, developers should always do white box testing, and sometimes (depending on your environment, methodology and application)testers, too.
Why? Read some topics on this subject (using the search function of these forums) and you'll find a lot of explanations.
Now, let me give you some advices about posting on these forums:
- first, see if there are other active topics with same subject, and read them. You could be surprized to find the answers before asking the question.
- use the search function to see if somebody else have asked this before.
- make the subject less general. For example, you could use following subject: "Who should do white box testing?". That way, you increase the probability to get answers.
- try to post your question in the most appropiate forum.
... Not even me.
White box testing will be always done by programmers only.
Definition: White box testing is the process of conduction the test on the internal functionality of the fuctions which are used to develop the product. And simply white-box testing means how it is developed.
In white box testing code is always visible and it will be done by programmers only at the time of development itself.
White box testing will be done at Unit and integration levels of testing.
White box testing is of four types:
1.Basis path testing 2.control structure testing 3.Procedure testing and 4.Loops testing.