DEV Community

Cover image for Functional Testing VS Non Functional Testing_Task3
Bala Venkatesh
Bala Venkatesh

Posted on

Functional Testing VS Non Functional Testing_Task3

Purpose - Functional Testing
To validate software whether it is functioning as expected and meets requirements.

Validation

Purpose - Non Functional Testing
Focus more on system's non functional aspects such as performance, reliability, compatibility, security.

reliable

Types - Functional testing

Unit Testing - Checks particular function or module works fine
Example:Testing login functionality functions

Integration Testing - Checks integration between different functions
Example:Testing interaction between shopping page and cart page

Interface Testing - Checks interaction between two different systems.
Example:Testing interaction between amazon and bank payment systems

Regression Testing - Retesting is done to ensure new functional doesn't interrupt existing one's.

Example : Addition of new UPI payment option doesn't affect existing functions.

Types - Non Functional testing
Document testing - Review of documents(BRS,test design,TSR)

Installation testing - Focus on installation ,setup, config, uninstallation.

Performance testing - checks speed, responsiveness, scalability and ensures data traffic by load ,stress and scalability testing.

Reliability testing - checks system performs consistently and accurately(resolves crash and unexpected behaviour)

Security testing - identifies vulnerabilities and assess Software ability to protect confidentiality.

Benchmark - Functional Testing
Success is based on status/result of functionality.

Test status

Benchmark - Non Functional Testing
Success is based on application's response, speed, usability.
performance

Top comments (0)