Action sequencer

[mlambley]

"Do this action and check the response against the schema. Then do that action and check the response against the schema as well as against the data in the first response".

This will allow us to build complex workflows rather than just "create, get, update, get, delete, get".

Details are still fuzzy. More to come.

[mlambley]

So far we have a single class (like a cest) which defines each step (create, get, update, delete).

Then we have entities like customers and employees which are mapped to a create url, get url, etc.

Then we have workflows which contain a series of actions. Each action groups entities and their steps together. Create a customer, then create an employee, then update a customer, then delete the employee, we can mix it up however we want.

Passing the data between each of the actions is the current hold-up.