---
title: Functional testing
slug: functional-testing
qid: 
snapshot: enwiki-001361058581
content_hash: 
license: CC BY-SA 4.0
source: https://en.wikipedia.org/w/index.php?oldid=1361058581
tags: [22909999, 23038230, 23118434, 23603337, 24043274, 24745122, 26083081, 65710263]
---

# Functional testing

> [!note] Provenance
> Snapshot `enwiki-001361058581` · content root `…`
> Derived from <https://en.wikipedia.org/w/index.php?oldid=1361058581> · Licensed CC BY-SA 4.0

In software development, functional testing is a form of software testing that verifies whether a system meets its functional requirements. Generally, functional testing is black-box, meaning the internal program structure is ignored (unlike for white-box testing). Sometimes, functional testing is a quality assurance (QA) process. As a form of system testing, functional testing tests slices of functionality of the whole system. Despite similar naming, functional testing is not testing the code of a single function. The concept of incorporating testing earlier in the delivery cycle is not restricted to functional testing.

In software development, functional testing is a form of software testing that verifies whether a system meets its functional requirements. Generally, functional testing is black-box, meaning the internal program structure is ignored (unlike for white-box testing). Sometimes, functional testing is a quality assurance (QA) process. As a form of system testing, functional testing tests slices of functionality of the whole system. Despite similar naming, functional testing is not testing the code of a single function. The concept of incorporating testing earlier in the delivery cycle is not restricted to functional testing. ===Sanity testing=== ===Smoke testing=== ===Regression testing=== ===Usability testing=== ==Six steps== Functional testing typically involves six steps 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 To check whether the application works as per the customer need ==See also==
