Jean-Baptiste Barth 61bb550052 Ensure activity and decision tasks cannot progress on a closed workflow ... This is a second barrier because I'm a little nervous about this and I don't want moto/swf to make any activity progress while in the real world service, it's strictly impossible once the execution is closed. Python doesn't seem to have any nice way of freezing an object so here we go with a manual boundary...		2015-11-19 11:45:26 +01:00
..
__init__.py	Reorganize SWF tests so they're shorter and easier to use	2015-11-19 11:45:24 +01:00
test_activity_task.py	Ensure activity and decision tasks cannot progress on a closed workflow	2015-11-19 11:45:26 +01:00
test_decision_task.py	Ensure activity and decision tasks cannot progress on a closed workflow	2015-11-19 11:45:26 +01:00
test_domain.py	Ensure activity and decision tasks cannot timeout on a closed workflow	2015-11-19 11:45:26 +01:00
test_generic_type.py	Fix random list ordering bugs on python 3.x in moto/swf tests	2015-11-19 11:45:26 +01:00
test_history_event.py	Fix timestamps in tests as Travis builds run on GMT time	2015-11-19 11:45:26 +01:00
test_workflow_execution.py	Implement start to close timeout on SWF workflow executions	2015-11-19 11:45:26 +01:00