Non-Functional System Testing Task

A Non-Functional System Testing Task is a system testing task that focuses on non-functional requirements.

• Example(s):
  • Baseline Testing;
  • Compliance Testing;
  • Documentation Testing;
  • Endurance Testing;
  • Load Testing;
  • Localization Testing and Internationalization Testing;
  • Software Performance Testing;
  • Recovery testing;
  • Resilience testing;
  • Security testing;
  • Scalability testing;
  • Stress testing;
  • Usability testing;
  • Volume testing;
• Counter-Example(s):
  • Functional Testing (of functional requirements).
• See: Performance Engineering, Reliability Engineering, Scalability, Compliance Testing, Documentation Testing, Endurance Testing, Load Testing, Software Performance Testing.

---

---

References

2019

• (Wikipedia, 2019) ⇒ https://en.wikipedia.org/wiki/non-functional_testing Retrieved:2019-11-21.
  • Non-functional testing is the testing of a software application or system for its non-functional requirements: the way a system operates, rather than specific behaviours of that system. This is in contrast to functional testing, which tests against functional requirements that describe the functions of a system and its components. The names of many non-functional tests are often used interchangeably because of the overlap in scope between various non-functional requirements. For example, software performance is a broad term that includes many specific requirements like reliability and scalability.

    Non-functional testing includes:

    • Baseline testing
    • Compliance testing.
    • Documentation testing.
    • Endurance testing.
    • Load testing.
    • Localization testing and Internationalization testing
    • Performance testing.
    • Recovery testing.
    • Resilience testing
    • Security testing.
    • Scalability testing.
    • Stress testing.
    • Usability testing.
    • Volume testing.

2018

• http://reqtest.com/testing-blog/functional-vs-non-functional-testing/
  • QUOTE: We’ve already spoken of functional and non-functional requirements, but the difference between these two types of requirement is again apparent when we get to the testing phase. Consequently, we also need to know about Functional and Non-Functional Testing
  • What is Functional Testing?

    Functional testing is concerned only with the functional requirements of a system or subsystem and covers how well (if at all) the system executes its functions. These include any user commands, data manipulation, searches and business processes, user screens, and integrations.

    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.

  • What is Non-Functional Testing?

    Non-functional testing is concerned with the non-functional requirements and is designed specifically to evaluate the readiness of a system according to the various criteria which are not covered by functional testing.

  • For example, in functional testing it might be revealed that the function of inputting data into a set of cells in a database works, however, usability testing (a part of Non Functional Testing) reveals that saving a version of the document requires 2 minutes, which will (or should) be judged as too long to wait.

    Essentially non-functional testing lets us measure and compare the results of testing the non-functional attributes of software systems, for example, by testing the application or system against the client’s requirement or a performance requirement.

    So basically, non-functional testing demonstrates how well the product behaves as opposed to simply what the product does.

---