Non-functional testing

From Wikipedia, the free encyclopedia

Template:Short description

Template:DMCA

Non-functional testing is testing software for its non-functional requirements: the way a system operates, rather than specific behaviors of that system. [1] This is in contrast to functional testing, which tests against functional requirements that describe the functions of a system and its components.

Types of non-functional testing

Accessibility testing

Accessibility testing is a non-functional testing activity that verifies whether a system, website, or application can be perceived, operated, and understood by people with a wide range of disabilities and whether it meets objective accessibility criteria such as the Web Content Accessibility Guidelines, WCAG success criteria. It typically combines automated checks, to detect obvious technical failures, manual inspection, to evaluate semantic structure, keyboard navigation, and ARIA usage, and human usability testing with people who have disabilities to assess real-world effectiveness and usability. Many government and organizational web standards now require WCAG conformance and explicitly treat accessibility as a mandatory non-functional quality attribute of public-facing digital services. Practical guides and industry overviews describe accessibility testing as a specialized subset of usability and non-functional testing that focuses on legal conformance, inclusive design, and measurable success criteria rather than functional feature behaviour alone.* [2] [3]

Baseline testing

Baseline testing is a non-functional activity that establishes a measured reference for key quality attributes (for example, response time, throughput, resource usage, error rates, and availability) against which future changes, releases, or configurations are compared. It usually occurs early in a release cycle or after a major environment change and combines controlled synthetic tests (benchmarks, scripted workloads, profiling) with monitored production observations to capture representative operating conditions. The baseline results are recorded as pass/fail thresholds, performance budgets, or trend series so regressions, capacity drift, and configuration-induced degradation can be detected quickly and triaged. Best practice is to store baseline test artifacts (test scripts, input datasets, environment definitions, and raw metrics) alongside the release so reruns are reproducible and comparisons remain meaningful across time.[4] [5]

Compliance testing

Template:Excerpt

Documentation testing

Template:Excerpt

Endurance testing

Template:Excerpt

Load testing

Template:Excerpt

Localization testing

Template:Excerpt

Reliability testing

Template:Excerpt

Recovery testing

Template:Excerpt

Software performance testing

Template:Excerpt

Security testing

Template:Excerpt

Scalability testing

Template:Excerpt

Stress testing

Template:Excerpt

Usability testing

Template:Excerpt

Volume testing

Template:Excerpt

See also

Lua error in mw.title.lua at line 404: bad argument #2 to 'title.new' (unrecognized namespace name 'Portal').

References

Page Template:Reflist/styles.css has no content.

  1. ^ Page Module:Citation/CS1/styles.css has no content."non-functional testing - ISTQB Glossary". ISTQB Glossary. International Software Testing Qualifications Board. Retrieved 2025-11-04.
  2. ^ Page Module:Citation/CS1/styles.css has no content.Lazar, Jonathan; Goldstein, Daniel; Taylor, Anne Marie (2015). Ensuring Digital Accessibility through Process and Policy. Elsevier. ISBN 978-0128006467.
  3. ^ Page Module:Citation/CS1/styles.css has no content.Yesilada, Yeliz; Harper, Simon (2019). Web Accessibility: A Foundation for Research. Springer. ISBN 978-1447174400.
  4. ^ Page Module:Citation/CS1/styles.css has no content."Baseline Testing". GeeksforGeeks. GeeksforGeeks. 2025-07-23. Retrieved 2025-11-04.
  5. ^ Page Module:Citation/CS1/styles.css has no content."Baseline Testing: What is it, and Why is it Important?". Testsigma Blog. Testsigma. 2025-06-26. Retrieved 2025-11-04.

Further reading

Page Template:Refbegin/styles.css has no content.

Script error: No such module "Sister project links".

Template:Software testing