Difference between Functional and Non-Functional Testing

Functional Testing: 

1. Testing the application against business requirements. Functional testing is done using the functional specifications provided by the client or by using the design specifications like use cases provided by the design team.
2. Functional testing is concerned only with the functional requirements of a system or subsystem and covers how well (if at all) the system executes its functions. These include any user commands, data manipulation, searches and business processes, user screens, and integrations.
3. Functional testing is done using the functional specifications provided by the client or by using the design specifications like use cases provided by the design team.

Following testing should consider in functional testing types:

• Unit Testing
• Smoke testing / Sanity testing
• Integration Testing (Top Down,Bottom up Testing)
• Interface & Usability Testing
• System Testing
• Regression Testing
• Pre User Acceptance Testing(Alpha & Beta)
• User Acceptance Testing
• White Box & Black Box Testing
• Globalization & Localization-testing

Non Functional Testing:

1. The non Functional Testing is the type of testing done against the non functional requirements. Most of the criteria are not consider in functional testing so it is used to check the readiness of a system. Non-functional requirements tend to be those that reflect the quality of the product, particularly in the context of the suitability perspective of its users. It can be started after the completion of Functional Testing. The non functional tests can be effective by using testing tools.
2. The testing of software attributes which are not related to any specific function or user action like performance, scalability, security or behavior of application under certain constraints.
3. Non functional testing has a great influence on customer and user satisfaction with the product. Non functional testing should be expressed in a testable way, not like “the system should be fast” or “the system should be easy to operate” which is not testable.
4. Basically in the non functional test is used to major non-functional attributes of software systems. Let’s take non functional requirements examples; in how much time does the software will take to complete a task? Or how fast the response is.

Following testing should consider in non functional testing types:

• Availability Testing
• Baseline testing
• Compatibility testing
• Compliance testing
• Configuration Testing
• Documentation testing
• Endurance testing
• Ergonomics Testing
• Interoperability Testing
• Installation Testing
• Load testing
• Localization testing and Internationalization testing
• Maintainability Testing
• Operational Readiness Testing
• Performance testing
• Recovery testing
• Reliability Testing
• Resilience testing
• Security testing
• Scalability testing
• Stress testing
• Usability testing
• Volume testing

Enjoy testing! If you like it above Testing related information then please kindly take a moment to share with your friends. You can add your suggestions/tips/questions below in the comments section. Definitely, I will try to answer of all questions as earliest.

You may also like:
Complete Testing Material

Testing basic interview questions