Test stub: Difference between revisions
No edit summary |
Courcelles (talk | contribs) Undid revision 350905762 by Thisarticleisastub (talk) Article already has an approperate stub template; at the bottom |
||
Line 1: | Line 1: | ||
{{computer-stub}} |
|||
{{Orphan|date=February 2009}} |
{{Orphan|date=February 2009}} |
||
In computer science, '''test stubs''' are programs which simulate the behaviors of software components (or modules) that are the dependent modules of the module being tested. |
In computer science, '''test stubs''' are programs which simulate the behaviors of software components (or modules) that are the dependent modules of the module being tested. |
Revision as of 02:37, 20 March 2010
In computer science, test stubs are programs which simulate the behaviors of software components (or modules) that are the dependent modules of the module being tested.
Test stubs provide canned answers to calls made during the test, usually not responding at all to anything outside what's programmed in for the test.[1]
Test Stubs are mainly used in incremental testing's Top-Down approach. Stubs are software programs which act as a module and give the output as given by an actual product/software.
Example
Consider a software program which queries a database to obtain the sum price total of all products stored in the database. However, the query is slow and consumes a large number of system resources. This reduces the number of test runs per day. Secondly, the tests need to be conducted on values larger than what is currently in the database.
The method (or call) used to perform this is get_total(). For testing purposes, the source code in get_total() could be temporarily replaced with a simple statement which returned a specific value. This would be a test stub.
There are several testing frameworks available and there is software that can generate test stubs based on existing source code and testing requirements.