DEV Community

Cover image for Functional Testing vs Non-functional Testing
Dhivya.R
Dhivya.R

Posted on

Functional Testing vs Non-functional Testing

Functional Testing
Non-Functional Testing

  1. Functional Testing: ✓ Checking the functionalities of the application.

• Manual Testing (Testing the functionalities by manual)
• Automation Testing (Testing the functionalities by using tools/scripts)
• Webservices Testing (Validating request and response) - API Testing
Automation Tools:
• Selenium - Web Based Applications
• Appium - Mobile Applications
• QTP (Quick Test Professional)/UFT (Unified Functional Testing) - Desktop Related
Applications [Ex: MS Office Applications, Web Browsers, etc.]
• Test Complete - Both Web Based and Desktop Based Applications

2. Non-Functional Testing:

✓Checking the non-functional aspects of the application.

Types of Non-Functional Testing:

  1. Performance Testing:

• They add the virtual number of users accessing the application simultaneously and at the same time

To check the performance of the application.

Tools Used:

• J-Meter Open-Source Tool

• Load Runner Paid Version

Load/Stress Testing:

• Process of adding load and making the application stress is called Load/Stress Testing.

  1. Usability Testing:

• To check how good the application is user friendly.

  1. Accessibility Testing:

• To check how well the application is accessible to different users.

• This testing mainly focuses on physically challenged peoples

• Tools Used: JAWS and NVDA

Top comments (0)