Functional Testing VS Non Functional Testing

Functional Testing:

• Test the functionality of the software.

• It has to be done before Non-Functional Testing.

• It is also called Behavioral testing and focuses on the underlying application features.

• It can be done manually, though test cases can be automated once the application is stable.

• Functional Testing types include Unit testing, Smoke testing, Integration testing, Regression testing, System testing, User Acceptance testing.

• Test data can be prepared using the business or functional requirements of the application.

• Example Test Case - Test whether the user is able to login into the application.

Non-Functional Testing:

• Test the Non-functional aspects or readiness of the software including performance, usability, reliability.

• It will be done after the Functional Testing completes.

• Focuses on the performance of the application.

• It's hard to do it manually. It usually needs already existing applications to measure and test application performance.

• Non-Functional Testing types include Volume testing, Load testing, Stress testing, Recovery testing, Scalability testing, Security testing.

• Test data can be prepared using the performance requirements of the application.

• Example Test Case - Time required to load the home page.