Non-Functionality Testing | Manual Testing Tutorial PDF

Non-Functionality Testing:

A complex level in system testing during which the testing team concentrates on extra characteristics of the software.
i.   Recovery Testing
ii.  Compatibility Testing
iii. Configuration Testing
iv.  Inter system Testing
v.   Installation Testing
vi.  Load Testing
vii. Stress Testing
viii.Data Volume Testing
ix.  Parallel Testing

i. Recovery Testing: -

It is also known as “Reliability Testing”. During this testing team validates that whether the software build changes from abnormal mode to normal mode.

ii) Compatibility Testing: -

Also Known as “Portability Testing”. During this test, the testing team validates whether the software build is running on customer expected platforms or not?
Platforms are Operating Systems, Compilers, Browsers & Other system software.

iii) Configuration Testing: -

It is also known as “Hardware compatibility test”. During this test, the testing team validates whether the software the software build is supporting different technologies, hardware devices or not?
Eg: Different printer technologies, various network technologies, etc.

iv) Inter System Testing:

It is also known “END – TO – END” Testing. During this test, the team validates whether the software build is co-existent with other software to share common resources or not?
Eg:

 v) Installation Testing: -

Below are the 3 key factors of installation
=> Setup Program Execution
=> Easy Installation of the Programs
=> Occupied Space

vi) Load Testing: -

The execution of our software build in a customer expected configuration environment under customer expected load to estimate performance is called “Load Testing or Scale Testing”. The load or scale means that the no. of concurrent users access our application build.
Eg:

*How make time is taken by the server to respond to each of the clients.

vii) Stress Testing: -

The execution of our software build in customer expected configured environment under various levels of load to estimate reliability is called “stress testing”.
Eg:

 * In this there will be many users.

viii) Data Volume Testing: -

During this test, the testing team estimates the peak limit of data handled by our software build.
Eg:

NOTE: This should be in terminology of customer.

ix) Parallel Testing: -

It is also known as “Comparative Testing” or “Competitive Testing”. During this test, the testing team is comparing the recent software build with previous versions of the software build or with the competitive software in market to estimate competitiveness. This testing is only applicable to software products.