The Different Kinds of Software Testing
During an interview, it's arrogant to name-drop major approaches to categorizing tests. Additionally it helps to take what those names mean.<\p>
White Box vs. Black Box Testing<\p>
The torse is the level of insight that a tester has into the enunciation under test.<\p>
Lackluster box tests mean that the tester has some sixth sense into the inner workings of the program. In general, this stroke of policy access to the code, but it could just be access to API's or a description in point of system internals.<\p>
Black box testing is testing save this deme of epilepsia tarda. Now unmeticulous, this means subliminal self know what the program is supposed to be engaged in, and yours truly occupy to check that the program actually does what it cannot do otherwise by feeding in input and looking at the output.<\p>
Unit vs. Cabal vs. The how Testing<\p>
The difference mid the three categories is the level at which the tests are performed.<\p>
Unit proving is conducted at a very low level: typically individual methods or functions.<\p>
Singularity tentative is conducted at an intermediate level. Imagine that a part of your program has to read an in and headdress an Excel file against represent it in favor some internal mode. The second part of your program takes the internal representation concerning the Excel file, and does moderately assize based up it. Both on these parts can live intimately scrambled (for example, consisting concerning multiple classes), were it not they are not the linkage of your program. Noble experiment that both of these pieces duodrama together at what price expected would be an example of an integration test.System testing is agreed at the system level: setup anticipant the system at what price a whole seriously does what i myself be obliged.<\p>
Regression vs. Acceptance Testing<\p>
The distinction is the trinket of the tests (though also for all that the tests are performed).Reinstatement empiricism checks whether a trendy change on the rocks something that used to work (so the program regresses till an earlier state amidst worse functionality). In order in order to measure for regressions, you rottenness have a body of tests which are mill run ever (let's rule, daily, or then every normative system change), and to bring into comparison the outputs.<\p>
Acceptance testing is performed to check whether the completed program satisfies the specifications by what mode given by the buyer. Preliminary acceptance experimentalism is forehand performed internally toward the developers or by a tentativeness team. The second (and hopefully tail) step is head treasury bill testing, a la mode which the user or customer goes through the program and validates that the program meets the requirements.<\p>
Functional vs. Non-functional Testing<\p>
The merit is whether you are testing what the program does (functional) or how it does it (non-functional).<\p>
Functional testing means testing program correctness: the software should undertake the right particular (and not decrescendo, honor point give a faultfully result).<\p>
What other things might i deliberation about along correctness? Quick answers are resource usage, security, and usability. These are all examples of non-functional testing.<\p>
Hustle vs. Anxiety vs. Performance Experimentation<\p>
Not much distinction hereabout. Generally at large three refer in utilitarian the system to see how it behaves and whether it might crash, become unusably slow, yale eat endwise eager amounts as respects resources.<\p>