What aspect of software is evaluated during non-functional testing?

Non-functional testing evaluates the operational characteristics and quality attributes of a system, rather than its specific features or functions. It answers the question of how well the system operates under various conditions. This includes assessing aspects like performance (speed, scalability), usability (ease of use), security (vulnerability to threats), and reliability (stability, uptime). Therefore, it focuses on the way a system operates and how it meets user expectations for quality and performance, which are not typically defined as discrete functional steps.

A. Specific behaviors and outputs of the system: This is the definition of functional testing, which verifies that the system does what it is supposed to do.
C. The creation of records and setting field values: This describes a specific use case or a unit test, which is a form of functional testing.
D. Functional requirements outlined in the design document: This is the input for functional testing, which validates that the system adheres to these specified requirements.

1. ServiceNow. (2023). Performance testing. ServiceNow Product Documentation. This document describes performance testing as a key type of non-functional testing focused on evaluating system speed, stability, and scalability under load.

2. ServiceNow. (2022). ServiceNow Performance Best Practices Guide. Introduction. The guide differentiates between functional correctness and performance/scalability, which are key non-functional attributes evaluated during non-functional testing.

3. ServiceNow Community. (2021). Blog: A Guide to ServiceNow Testing. This article clearly distinguishes between Functional Testing ("Does it work?") and Non-Functional Testing ("How well does it work?"), aligning with the correct answer.