Ivan A. Melnikov ea272ee743 Validate each flow state change ...

When engine changing state, the transition is now validated. This
helps to avoid complex and error prone checks in engine._change_state
and make validating code more reusable in different engines.

Change-Id: I2a06823c532926bb3bd034f7252b14bdbbc1fa1d
Implements: bp:transition-control

2013-10-07 16:46:02 +04:00

..

persistence

Correctly save task versions

2013-10-05 09:51:45 +04:00

__init__.py

Begin adding testing functionality

2013-05-13 22:26:54 -07:00

test_action_engine.py

Update state sequence for failed flows

2013-10-07 16:42:40 +04:00

test_check_transition.py

Validate each flow state change

2013-10-07 16:46:02 +04:00

test_flattening.py

Check for duplicate task names on flattening

2013-10-05 09:51:45 +04:00

test_flow_dependencies.py

Verify provides and requires

2013-09-18 09:51:33 +04:00

test_functor_task.py

Simpler API to load flows into engines

2013-10-03 10:08:55 +04:00

test_linear_flow.py

Update state sequence for failed flows

2013-10-07 16:42:40 +04:00

test_progress.py

Simpler API to load flows into engines

2013-10-03 10:08:55 +04:00

test_storage.py

Validate each flow state change

2013-10-07 16:46:02 +04:00

test_task.py

Allow to specify default provides at task definition

2013-09-19 11:09:05 +04:00

test_unordered_flow.py

Simpler API to load flows into engines

2013-10-03 10:08:55 +04:00

test_utils_failure.py

Wrapping and serializing failures

2013-10-04 12:10:27 +04:00

test_utils.py

Wrapping and serializing failures

2013-10-04 12:10:27 +04:00