Non-functional testing (draft)

Draft — quality attributes that aren’t “does this user story pass?” Complements Testing strategy and React testing; I’ll flesh this out when I recover slide material.

What counts here

• Performance — budgets, Core Web Vitals, load/soak for APIs.
• Accessibility — automated axe checks, keyboard flows, screen reader spot checks.
• Security — SAST/dependency scanning (see CI notes), authn/z contract tests where relevant.
• Reliability / resilience — chaos or failure injection for critical paths (often backend-heavy).
• Internationalization — locale switching, RTL, string overflow, date/number formatting.
• Visual regression — screenshot diff for design systems or high-risk pages.

Relationship to functional tests

Functional tests ask “did the feature work?” Non-functional tests ask “is it acceptable under constraints?” (latency, WCAG, no critical CVEs, etc.). Some checks live in the same pipeline (lint, Lighthouse CI, axe in Playwright); others are periodic or environment-specific.

Next

Cross-link concrete tools I actually run in GitLab and local dev once I write them down.