Talk:Functional testing
This article is rated Stub-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||
|
Redirect
editI'm not so sure I agree that functional and acceptance tests are the same. I do agree that functional and black box are the the same. Here's some definitions from my SQE certification training manual:
Acceptance testing: Formal testing with respect to user needs, requirements, and businesss processes conducted to determine whether or not a system satisfies the acceptance criteria and to enable the user, customers or other authorized entity to determine whether or not to accept the system. [After IEEE 610]
Black-box testing: Testing, either functional or non-functional, without reference to the internal structure of the component or system.
Functional testing: Testing based on an analysis of the specification of the functionality of a component or system. See also black box testing.
DRogers 13:42, 19 January 2007 (UTC)
- I agree. This article differentiates between functional and system testing:
- "The objective of function test is to measure the quality of the functional (business) components of the system."
- "The objective of system test is to measure the effectiveness and efficiency of the system in the "real-world" environment."
- --IAmAI (talk) 16:25, 21 February 2008 (UTC)
Innacurate
edit"Functional testing is a quality assurance (QA) process[1] and a type of black box testing"
Functional Testing is not a Quality Assurance process any more than Software Development is. Testing and Quality Assurance are not the same thing and should not be lumped together, especially with a vague statement such as that. Quality Assurance is analysis and control of the entire Software Development LifeCycle, from Requirements Gathering through Sunset.
Functional Testing is also not "a type of Black Box Testing", Black Box Testing is an approach to Functional Testing, and a very weak and expensive approach at that.
This author is uninformed...
Frank Miller Quality Assurance Guru --68.178.122.62 (talk) 23:35, 24 February 2015 (UTC)
Innacurate
editUsability testing is listed on the non-functional testing page. It shouldn't be listed here on the functional testing page. — Preceding unsigned comment added by Kiwistyler (talk • contribs) 20:59, 3 June 2015 (UTC)
6 steps
editFunctional testing can only check that the input conforms to the output, and not "whether the application works as per the customer need". The latter is a mixture of specs and implementation quality, and it is much better covered by acceptance testing by external parties (beta testing). — Preceding unsigned comment added by Lucian.ciufudean (talk • contribs) 08:02, 8 February 2018 (UTC)