As soon as the static testing stage of the product is over, we move on to the business end of the deal. How well the software product will behave in the real world scenario. What will be its performance output, as regards security, load and the like? Answer to these queries is dynamic testing.
Performed in an environment where the code is actually executed, dynamic testing is used for checking the functional behaviour of the system and to see to it, that it is in conformance with the user expectations and requirements.
As per their utility, different techniques of dynamic testing are employed for varied scenarios.
We present list of few of those techniques:-
Generally run by software developers, unit testing involves testing of small fragments of the source code such as operational procedures or individual functions, independent of each other. One particular benefit of this approach is the easy incorporation of changes at a later date.
Immediately performed after unit tests, integration testing involves the grouping of individual modules and testing their efficacy as a whole. This helps determine the fact that all modules of the source code are behaving as expected.
A form of Black box strategy, system testing is done to evaluate the compliance of the system performance with the specifications mentioned in the owner manual. It includes GUI testing.
Acceptance testing is conducted to determine if the requirements of the product specifications are being met as per the contractual obligations at the site.
It has variants by the name of Alpha beta tests, Contract and regulation acceptance testing, physical tests, etc.
There are number of dynamic testing tools that are used in dynamic testing. Click the link to explore these tools in details.