Testing the Functionality of the System

Functional testing is a quality assurance (QA) process 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.
Functional testing usually describes what the system does.
Functional testing ^[1] differs from system testing in that functional testing "verifies a program by checking it against

1. design documents or
2. specifications,

while system testing "validates a program by checking it against the published user or system requirements" .

1. Develop a test plan that outlines the objectives, resources, and procedures for testing the system.
2. Prepare test cases and test data that will be used to evaluate the system's functionality.
3. Configure the test environment to match the intended production environment as closely as possible.
4. Execute the test cases and document the results.
5. Evaluate the results to determine if the system functions as expected and meets the requirements outlined in the test plan.
6. Identify and document any defects or issues that were identified during testing.
7. Retest the system after any defects have been corrected to ensure they have been properly addressed.
8. Perform any necessary additional testing or validation, such as user acceptance testing or performance testing.
9. Prepare a report on the testing process and the results obtained.
10. Implement the system if it passes all test.

[1] Functional testing: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.