Techniques For Software Testing

June 14, 2011 - PRLog -- Nowadays we have a lot of various methods for testing. And some of them can be applied to more than one test phase. But you should remember that none of them guarantees software without bugs: each has its own strengths, costs and limitations.
Well, let’s talk about most spread techniques for software testing. There are such methods:
1). Static analysis methods
The best use for these techniques is before integration, and it can also point to the need for more-rigorous unit testing. These require using tools to analyze the source code.
2). Dynamic analysis techniques
In this case techniques are derivative methods which undertake that some technique such as object-orientation, finite state machines, condition tables, or functional programming, has been used to develop the software.
We use this information to determine the test cases, so these have unique areas of application. These can be applied at both unit test times and system test. These are generally applied to unit tests.
3). Structural (white-box) methods
These techniques can also be used on any unit or build, but are inexpensive to devise when used on structured programs. These are generally applied to unit tests.
4). Functional (black-box http://qatestlab.com/company/software-testing-glossary/bl...) techniques
Black-box techniques can be applied to any unit, build, or system, since they undertake no information of how either was built or what it consists of. Such techniques order an adequate and unequivocal specification if they are to be efficient. (Devising black-box tests for some code from its specification at the time the specification is written is a useful verification of the specification; in the case when it can’t be performed, the specification isn’t good enough.) You will ordinarily do it for a system test.
5). Symbolic evaluation
Symbolic estimation realized by an automated symbolic estimation implement places no particular requirement on the unit, except that it is in the language estimated by the implement. This involves “dry-running” the code, and recording the output values of variables algebraically rather than using specific values for input variables http://qatestlab.com/company/software-testing-glossary/in.... This is commonly applied to unit tests.

# # #

QATestLab is independent, offshore software testing company located in Kiev, Ukraine. QATestLab performs testing of products on each stage of software development cycle.