Functional testing is primarily concerned with “what” a system does rather than “how” it does it.
Control flow models and menu structure models are used primarily in functional testing.
Functional testing includes, but is not limited to, load testing, stress testing and reliability testing.
Functional testing is often referred to as “structural” testing by testers and developers.
To decide if the system is ready for detailed and further testing.
To determine how the existing system may be affected by changes.
To make use of every possible input condition as a test case.
To determine if a system can function correctly with invalid inputs.
I, ii & iii
Ii & iii
I & iv
Iii & iv
To help the developer to compare differences between files and databases.
To reduce the quantity of component tests needed to be run.
To make it easier for developers to test each other’s code.
To simplify running unit tests when related components are not available yet.
All of the factors should be taken into account.
I & iii
I, iii & iv
I, ii, iv & v
Structure-based testing (white box)
Functional testing (black box)