Functional Testing Task
Jump to navigation
Jump to search
A Functional Testing Task is a quality assurance task that ...
- …
- Counter-Example(s):
- See: Verification and Validation (Software), Usability Testing, Black-Box Testing, White-Box Testing, Requirement, System Testing, Smoke Testing (Software), Sanity Testing, Regression Testing, A/B Testing.
References
2019
- (Wikipedia, 2019) ⇒ https://en.wikipedia.org/wiki/functional_testing Retrieved:2019-8-23.
- Functional testing is a quality assurance (QA) process[1] and 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 (unlike white-box testing).[2] Functional testing is conducted to evaluate the compliance of a system or component with specified functional requirements. Functional testing usually describes what the system does.
Functional testing does not imply that you are testing a function (method) of your module or class. Functional testing tests a slice of functionality of the whole system.
Functional testing differs from system testing in that functional testing “verifies 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 has many types:
- Functional testing is a quality assurance (QA) process[1] and 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 (unlike white-box testing).[2] Functional testing is conducted to evaluate the compliance of a system or component with specified functional requirements. Functional testing usually describes what the system does.