Skip to content

Fix typo #65

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fix typo #65

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion benefit-handle-anomalies.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,4 +10,4 @@ In a lot of bottom-up approaches, it is common to forego the error states: When

In a statechart approach, failures are generally failures of background [activities](glossary/activity.html){:.glossary}. When a background activity fails, a simple thing to do is to inform the statechart about the failure (by sending an [event](glossary/event.html){:.glossary} that describes the error), and describe _in the statechart_ how the failure should be handled, typically by introducing a new [transition](glossary/transition.html){:.glossary} to deal with the error.

This simple act causes the error to be explicitly visible in the statechart, _and_ therfore to the development team and other stakeholders. It allows [QA teams to discover](benefit-qa-exploration-tool.html) that the error state exists, possibly prompting them to actually test this path. It allows designers to design the error states [that have been uncovered](benefit-all-states-explored.html).
This simple act causes the error to be explicitly visible in the statechart, _and_ therefore to the development team and other stakeholders. It allows [QA teams to discover](benefit-qa-exploration-tool.html) that the error state exists, possibly prompting them to actually test this path. It allows designers to design the error states [that have been uncovered](benefit-all-states-explored.html).