Quality Testing

Quality is delighting customers

Views: 1809

Reply to This

Replies to This Discussion

When testing is done to check,   "What software does...??" is called functional testing ..!

When testing is done to check , "How well software does something .??" is called non-functional testing ..!


Samrat -

I completely agree with you Samrat.

This couldn't have been answered in a simpler way.


Milin Patel


  1. Functional Testing: 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.


  1. Non-Functional Testing


  • Usability testing: Testing technique which verifies the ease with which a user can learn to operate, prepare inputs for, and interpret outputs of a system or component. It is usually performed by end users
  • Performance testing: Functional testing conducted to evaluate the compliance of a system or component with specified performance requirements. It is usually conducted by the performance engineer.
  • Load testing: Testing technique that puts demand on a system or device and measures its response. It is usually conducted by the performance engineers.



  • Stress testing: Testing technique which evaluates a system or component at or beyond the limits of its specified requirements. It is usually conducted by the performance engineer.
  • Security testing: A process to determine that an information system protects data and maintains functionality as intended. It can be performed by testing teams or by specialized security-testing companies.
  • Configuration testing: Testing technique which determines minimal and optimal configuration of hardware and software, and the effect of adding or modifying resources such as memory, disk drives and CPU. Usually it is performed by the performance testing engineers.
  • Compatibility testing: Testing technique that validates how well software performs in a particular hardware/software/operating system/network environment. It is performed by the testing teams.
  • Install ability testing: Quality assurance work that focuses on what customers will need to do to install and set up the new software successfully. It may involve full, partial or an upgrade install/uninstall processes and is typically done by the software testing engineer in conjunction with the configuration manager.
  • Availability testing: Availability Testing is different from Performance Testing as it focuses on aspects like up-time of application and IT infrastructure. In addition, this includes running an application for a planned period of time, collecting failure events and repair times, and comparing the availability percentage to the original service level agreement.
  • Volume testing: Testing which confirms that any values that may become large over time (such as accumulated counts, logs, and data files), can be accommodated by the program and will not cause the program to stop working or degrade its operation in any manner. It is usually conducted by the performance engineer.

Functional Testing:Functional testing is what a system is supposed to do?
 (e.g. interoperability)

Non-Functional Testing means How a system is supposed to do?
(e.g. Efficiency,accuracy.)



Functional and Non-Functional Testing both are part of Application Assurance.

Functional Testing services consist of the following:

  • System Integration Testing
  • User Acceptance Testing
  • Test Automation
  • Data Verification

Non-Functional Testing services span the following:

  • Performance Testing
  • Compatibility Testing
  • Disaster Recovery (DR) Testing

Functional Testing is nothing but the real functionalities of the application.  Eg.  Take Facebook - Like, Share, Comment are the functionalities to be tested.  

Non functional Testing - the performance of the application.  Eg. How much time facebook.com takes when 10 lakh customers logged in, how facebook.com behaves, when we share a huge video / image there.

So non functional testing is only performance of the application? 

No , apart from Performance testing will include..

Browser compatibility testing-->Testing the application across different browsers like Chrome,Safari,IE,Mozilla etc.

Load Testing --> Increasing the number of users,reducing the hardware resources etc. and check application performance at peak time.

Usability Testing -->The ease how u can  use the application

The major difference between functional and non-functional testing is: Functional testing ensures that your product meets customer and business requirements, and there have any major bugs.
Non-functional testing wants to see if the product stands up to customer expectations.
Basically, functional testing is designed to determine that the application’s features and operations perform the way they should. Non-functional testing wants to know that the product “behaves” correctly.

Here is an answer to your query. Please check this link - http://bit.ly/21UXRVj

functional testing: checking the functionality of an application.checking against the business requirements.

Non functional testing:checking apart from the functionality of an application.like performance testing(load testing,stress testing,scallability testing)

Non-functiobal testing:

The non functional Testing is the kind of testing done against the non functional needs. The vast majority of the criteria are not considered in functional testing so it is utilized to check the availability of a system. Requirements which are non functional have a tendency to be those that mirror the nature of the product, especially with regards to the reasonableness perspectives of its clients.

Non functional testing affects client and client satisfaction with the product. Non functional testing is expected to be told in a testable manner “the software should be fast” or “the software ought to be easy to operate” which is not testable.

Here is some testing that should be considered in the non functional testing types:

  • Load testing

  • Reliability testing

  • Performance testing

  • Security testing

Functional testing:

It includes the complete integration framework to check the system’s consistence with its predetermined requirements. In view of the system requirement specification document, this kind of testing is to be done. In actual testing, testers need to confirm a particular activity or functioning of the code. For functional testing either manual testing or automation tools can be utilized however functionality testing would be simpler utilizing manual testing as it were.

Five stages required to remember in case of Functional testing:

  • Arrangement of test data in light of the requirements of the function.

  • Business necessities are the inputs to functional testing.

  • In light of functional specifications, discover of output of the functions.

  • Executing the test cases.

  • Watch the actual and expected results.

Functionality testing confirms that an application is still completely functional after localization. Indeed, even applications which are professionally internationalized by world-readiness rules require functional testing.


TTWT Magazine





© 2020   Created by Quality Testing.   Powered by

Badges  |  Report an Issue  |  Terms of Service