You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For product stability, I think it could be improved by also measuring how it saves information in case of a crash. I don’t think any product can be 100% crash-proof, so making sure there are systems in place in case of a crash should be measured in stability.
The text was updated successfully, but these errors were encountered:
Thanks for your comment! In the Digital Standard under Product Stability, there is an Indicator that says if the program crashes, it "shuts down in a safe and responsible fashion", which could cover this concept. If you'd like to see this addressed more directly, please suggest (or enter a pull request for) specific wording for a revised or new indicator, as well as your thoughts on how and what to measure to determine this in testing. Thanks!
For product stability, I think it could be improved by also measuring how it saves information in case of a crash. I don’t think any product can be 100% crash-proof, so making sure there are systems in place in case of a crash should be measured in stability.
The text was updated successfully, but these errors were encountered: