in addition e.g. ...there are some more types which fall under both Black box and White box testing strategies such as: Functional testing (which deals with the code in order to check its functional performance), Incremental integration testing (which deals with the testing of newly added code in the application), Performance and Load testing (which helps in finding out how the particular code manages resources and give performance etc.) etc. (from: www.buzzle.com/editorials/4-10-2005-68350.asp )
here you have one post about yellow box and red box: groups.google.com/group/software-testing/browse_frm/thread/f45d6bc9d4bc8842/877969bb8fb7742e?lnk=st&q=yellow+box+test&rnum=6#877969bb8fb7742e
Acceptance testing, often referred to as Red-Box testing. [Hetzel88] they mention as source: Hetzel, Bill: The Complete Guide to Software Testing, QED Information Sciences, Wellesley, Mass. 1988, p. 73
here is the complete passage from Goeschl + Sneed:
In addition, there are four distinct levels of testing to be done: • Module or class testing, often referred to as White-Box testing, • Integration testing, often referred to as Grey-Box testing, • System testing, often referred to as Black-Box testing, and • Acceptance testing, often referred to as Red-Box testing. [Hetzel88]
The testing of individual classes can be handled with the help of existing unit test tools such as TestBed, Cantata, and JUnit. [BeGa98] System testing can also be done using conventional capture/replay and database editing tools. [Beizer95] Acceptance testing represents a greater challenge in the case of distributed systems, but it is not critical if the other tests have been performed well. The greatest challenge is that of integration testing. Distributed systems consist of a large number of interacting components executing in diverse environments with complex interfaces. These interactions and their interfaces have to be verified and validated by integration testing since neither unit nor system testing suffices for this purpose. The only way to accomplish this in an effective and efficient manner is via automated tests. As pointed out by D.Graham and M.Fewster in their work on test automation, test tools may not replace human intelligence in testing, but without them testing complex systems at a reasonable cost will never be possible. [FewGra99]
BTW: does it have to be boxes or can it also be circles?
Perhaps the definitions of BlackBox and WhiteBox are not good enough, so that they fit for all testing methods? I mean who says, that the BB and WB terminology should be stable for the future?
Why not classify/group with other characteristics? You have some ideas?
Post edited by: admin, at: 2006/11/05 16:01
The administrator has disabled public write access.
