Definition: A quality signal is the information a team uses to judge software quality. In traditional testing the signal is test results: passes and fails. In TestOps, the signal becomes telemetry and other data from the live system, interpreted through patterns and key performance indicators.
So what? What you treat as your signal shapes what you can learn. Moving from test results to production data lets teams see how software actually behaves for real users, not only how it behaves in a test environment.
Examples: Treating task completion times across millions of users as a performance signal. Comparing data from an old and new version of a feature during an A/B test.
