Functional testing: Difference between revisions
Content deleted Content added
No edit summary |
|||
| Line 21: | Line 21: | ||
==Notes== |
==Notes== |
||
{{Reflist}} |
{{Reflist}} |
||
==External links== |
|||
*[http://www.corelis.com/blog/index.php/blog/2011/01/10/jtag-for-functional-test-without-boundary-scan JTAG for Functional Test without Boundary-scan] |
|||
{{DEFAULTSORT:Functional Testing}} |
{{DEFAULTSORT:Functional Testing}} |
||
Revision as of 17:51, 30 August 2011
 | Template:Wikify is deprecated. Please use a more specific cleanup template as listed in the documentation. |
 | This article needs additional citations for verification. (December 2010) |
Functional testing is a type of black box testing that bases its test cases on the specifications of the software component under test. Functions are tested by feeding them input and examining the output, and internal program structure is rarely considered (Not like in white-box testing).[1]
Functional testing differs from system testing in that functional testing "verif[ies] a program by checking it against ... design document(s) or specification(s)", while system testing "validate[s] a program by checking it against the published user or system requirements"(Kaner, Falk, Nguyen 1999, p. 52).
Functional testing typically involves five steps[citation needed]:
- The identification of functions that the software is expected to perform
- The creation of input data based on the function's specifications
- The determination of output based on the function's specifications
- The execution of the test case
- The comparison of actual and expected outputs
See also
Notes
- ^ Kaner, Falk, Nguyen. Testing Computer Software. Wiley Computer Publishing, 1999, p. 42. ISBN 0-471-35846-0.
External links
 | This computing article is a stub. You can help Wikipedia by expanding it. |