What are Non Functional Testing Types

How to perform non Functional Testing

Performing non-functional testing involves evaluating the attributes of a system that are not related to specific behaviors or functions but rather focus on aspects like performance, security, reliability, and usability. Here’s a general guide on how to perform non-functional testing:

1. Understand Requirements:

   • Identify non-functional requirements specified in the project documentation or gather them from stakeholders.
   • Non-functional requirements may include performance goals, security measures, scalability expectations, usability criteria, etc.

2. Plan Non-functional Testing:

   • Develop a non-functional testing strategy that outlines the scope, objectives, and resources needed for testing.
   • Determine the types of non-functional testing that are relevant to your application.

3. Select Tools and Environment:

   • Choose appropriate tools for non-functional testing. For example, use performance testing tools like JMeter or LoadRunner for load testing.
   • Set up the testing environment to simulate real-world conditions.

4. Performance Testing:

   • Load Testing:
     • Create test scenarios that simulate expected user loads.
     • Execute tests to measure system response times and identify performance bottlenecks.
   • Stress Testing:
     • Apply loads beyond the system’s capacity to identify breaking points and weaknesses.
   • Volume Testing:
     • Test the system with a large volume of data to ensure it can handle the expected data sizes.

5. Security Testing:

   • Vulnerability Testing:
     • Use security testing tools to identify vulnerabilities in the system.
     • Perform code reviews and analysis for security issues.
   • Penetration Testing:
     • Simulate real-world attacks to assess the system’s resilience to security threats.

6. Usability Testing:

   • User Experience Testing:
     • Evaluate the overall user experience by involving real users or usability experts.
     • Collect feedback on the system’s usability.
   • Accessibility Testing:
     • Test the application’s accessibility for users with disabilities.

7. Compatibility Testing:

   • Browser Compatibility Testing:
     • Test the application on different web browsers to ensure consistent behavior.
   • Operating System Compatibility Testing:
     • Verify that the application works correctly on various operating systems.

8. Maintainability Testing:

   • Portability Testing:
     • Test the application on different hardware and software configurations.
     • Check if the application can be easily ported to different environments.
   • Upgradability Testing:
     • Evaluate the process of upgrading the application to newer versions.

9. Scalability Testing:

   • Concurrency Testing:
     • Assess the system’s ability to handle multiple users or transactions simultaneously.

10. Recovery Testing:

    • Disaster Recovery Testing:
      • Simulate disaster scenarios and assess the system’s ability to recover.

11. Document and Analyze Results:

    • Record and analyze the results of non-functional tests.
    • Identify any performance bottlenecks, security vulnerabilities, or usability issues.

12. Iterate and Improve:

    • Use the insights gained from testing to make improvements to the system.
    • Iterate through the testing process as needed to address any issues found.

13. Report and Communicate:

    • Prepare and share comprehensive reports with stakeholders.
    • Communicate findings, recommendations, and potential risks associated with non-functional aspects of the system.

Remember that non-functional testing is an ongoing process, and it may need to be repeated as the application evolves or as new requirements emerge. Regularly reviewing and updating non-functional tests helps ensure that a system continues to meet performance, security, and usability expectations.