Week 7 Workflow Example
- Complete the tests of the Technology Workflow (make it up)
- Or create your own Object and Workflow
Developing and Testing Workflows
What is workflow?
Workflow is a finite-state-machine-inspired API for modeling and interacting with what we tend to refer to as 'workflow'.
A lot of business modeling tends to involve workflow-like concepts, and the aim of this library is to make the expression of these concepts as clear as possible, using similar terminology as found in state machine theory.
So, a workflow has a state. It can only be in one state at a time. When a workflow changes state, we call that a transition. Transitions occur on an event, so events cause transitions to occur. Additionally, when an event fires, other arbitrary code can be executed, we call those actions. So any given state has a bunch of events, any event in a state causes a transition to another state and potentially causes code to be executed (an action). We can hook into states when they are entered, and exited from, and we can cause transitions to fail (guards), and we can hook in to every transition that occurs ever for whatever reason we can come up with.
Review the Workflow Gem documentation.
- Fork and clone this repository to make your own, called yourname-week-07-workflow.
- Add yet another workflow state and a spec for it. Or create your own workflow.
- Is it a one way workflow, or can it be rolled back? You decide.
Make sure you have an acceptible level of test coverage. Your test coverage percentage is your grade. Just kidding.
Tag it complete and push it back to github