The opposite of white box testing / API, which is covered here
There are many interviews, both for developers and qa, where you are asked to check smth out. Classic - check the save dialog from notepad .
Here is a list of tests that I can think of, classify and prioritize:
[functional, high] - the dialog fulfills its precedents - appears when the user performs "save as", the buttons on the left work, the file is saved with the specified name and encoding, the upper buttons work, the button is canceled.
[functional, medium] - save in read-only environment - does a pop-up error appear?
[functional, medium] - save an empty file
[functional, low] - save the file as .txt, but remove the extension from the name
[functional, high] - make sure the dialogue is modal
[functional, high] - make sure dir and dir navigation functions are working
[functional, high] - context menu options work
[load, low] - go to the directory where there is a very large (aproaching the system limit) number of TXT files; save the file there
[load, low] - go to the directory with a large number of subdirectories. save the file there.
[stress, low] - go to the directory with the maximum number of allowed files and try to save the file
[stress, low] - saturates the system with file descriptors (simulate applications that have very rich interfaces or handle leaks, such as Yahoo Messenger); Does a dialog appear?
[stress, medium] - , .
[, ] - , " "
[stress, low] -
[, ] - ,
[, ] - , (, , -); ,
[accessibility, high] - , , ? (, ); ,
[ , ] - , , ?
[, ] -
[, ] - UTF-8 ANSII
[, ] - .
[] - , , ,
[usability, high] - , ,
? ?