# Indicators for non-functional testing
<a name="indicators-for-non-functional-testing"></a>

Evaluate system attributes such as performance, usability, and reliability to ensure software meets operational requirements. This testing dimension focuses on how the system behaves, rather than specific functionalities.

**Topics**
+ [[QA.NT.1] Evaluate code quality through static testing](qa.nt.1-evaluate-code-quality-through-static-testing.md)
+ [[QA.NT.2] Validate system reliability with performance testing](qa.nt.2-validate-system-reliability-with-performance-testing.md)
+ [[QA.NT.3] Prioritize user experience with UX testing](qa.nt.3-prioritize-user-experience-with-ux-testing.md)
+ [[QA.NT.4] Enhance user experience gradually through experimentation](qa.nt.4-enhance-user-experience-gradually-through-experimentation.md)
+ [[QA.NT.5] Automate adherence to compliance standards through conformance testing](qa.nt.5-automate-adherence-to-compliance-standards-through-conformance-testing.md)
+ [[QA.NT.6] Experiment with failure using resilience testing to build recovery preparedness](qa.nt.6-experiment-with-failure-using-resilience-testing-to-build-recovery-preparedness.md)
+ [[QA.NT.7] Verify service integrations through contract testing](qa.nt.7-verify-service-integrations-through-contract-testing.md)
+ [[QA.NT.8] Practice eco-conscious development with sustainability testing](qa.nt.8-practice-eco-conscious-development-with-sustainability-testing.md)