| || |
gray level testing
waht is gray level testing?
i didn't get any theread for this in functions testing so posting it and awaiting for you valuable answers
Re: gray level testing
Just for clarification are you looking for grey-box testing or grey level testing. I don't think grey level testing is really talked about here, although it could refer to testing grey level images using different compressions as shown in the following article:
Let me do a quick explanation as I understand it of white, black and grey box testing.
White Box testing is where the tester intimately knows the code and internal workings of the system under test. (An example would be the tester going through each line of code and verifying inputs/outputs)
Black Box testing is where the tester has no knowledge of the code or the internal functionality of the system, all they know how it works via the interface or how the user would see it. (An example would be the tester submitting values to a form and then seeing at what is returned on the next page)
Grey Box testing is where the tester has some knowledge of the internal functionality of the system but maybe not down to each line of code. (An example would be the tester submits a form verifies what is returned on the next page and then goes to the database to verify that what they submitted shows up in the correct table(s) in the database)
Hopefully this makes sense. [img]images/icons/smile.gif[/img]
Re: gray level testing
Black Box Testing: Known Input, expected output, don't care what happens in between.Also called "functional Testing"
White Box: Testing flows through the code, code coverage testing, can be utilising understanding of the code to do Equivalence Partitioning etc, use of break points to check variable values, use of debuggers to check states, etc etc. Working with the code as well as it's "deliverables".
Also called "Structural Testing"
Grey Box: Can be mixture of above two test approaches, but might include understanding of componatisation, use of test harnesses (stubbs, whatever) - usually where interrim deliverables are to be tested prior to complete application is ready (e.g testing code with dependencies but prior to their availability).
I've never heard of Grey Level Testing (outside of perception or optical articles!). Could it be like DefCon 1, 2 3 etc... [img]images/icons/smile.gif[/img] [img]images/icons/blush.gif[/img]