Which statement best defines 'stable' in readiness criteria?

• A. The feature behaves consistently across scenarios and environments.
• B. It has no bugs at all.
• C. The feature is the newest feature.
• D. It is aesthetically pleasing.

Answer: (B)

Stable means you can rely on the feature to behave the same way across different scenarios and environments. It should perform consistently across browsers, devices, screen sizes, data inputs, user roles, and varying load conditions, so results aren’t flip-flopping or crashing in one setting but not another. This kind of predictability is what readiness criteria are aiming for, signaling to testers and users what to expect in production. While having zero bugs would be ideal, stability isn’t about defect absence; it’s about consistent, dependable behavior under real-world use. The other ideas miss the point: being the newest feature is about recency, not reliability; aesthetics are about appearance, not how the feature behaves; and claiming no bugs at all is an unrealistic standard for stability.