Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

system for crashes #152

Open
juliah484 opened this issue Jun 29, 2020 · 3 comments
Open

system for crashes #152

juliah484 opened this issue Jun 29, 2020 · 3 comments
Assignees
Labels
out of scope An issue that is not within the purview of the standard at present

Comments

@juliah484
Copy link

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.

@stephtngu-CR
Copy link
Collaborator

cc: @mrerecich for review

@mrerecich
Copy link
Collaborator

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!

@billfitzgerald
Copy link
Collaborator

Setting to "out of scope" per comment from @mrerecich

@billfitzgerald billfitzgerald added the out of scope An issue that is not within the purview of the standard at present label Oct 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
out of scope An issue that is not within the purview of the standard at present
Projects
None yet
Development

No branches or pull requests

4 participants