Joshua Harlow 16a2c791f0 Add a test that checks for task result visibility ...

Now that a task can provide the same thing that it
requires, having a nice little test that ensures what
is gotten is expected in a nice manner should be done
to make sure what a task will be getting for its arguments
respect the scoping that is defined by the flow ordering.

Change-Id: I1cdc5c3bd3f56b39f20f28f51c36017405150cea

2015-05-29 17:28:00 -07:00

..

__init__.py

Removed copyright from empty files

2014-02-22 17:16:29 +08:00

test_creation.py

Increase robustness of WBE producer/consumers

2015-01-20 15:07:56 -08:00

test_dispatcher.py

Make the dispatcher handler be an actual type

2015-02-15 20:21:24 -08:00

test_endpoint.py

Switch to using 'oslo_utils' vs 'oslo.utils'

2015-01-14 23:56:11 -08:00

test_executor.py

Abstract out the worker finding from the WBE engine

2015-01-31 23:03:25 -08:00

test_message_pump.py

Make the dispatcher handler be an actual type

2015-02-15 20:21:24 -08:00

test_pipeline.py

Switch to using 'oslo_utils' vs 'oslo.utils'

2015-01-14 23:56:11 -08:00

test_protocol.py

Move to using the oslo.utils stop watch

2015-03-20 17:40:24 -07:00

test_proxy.py

Use explicit WBE object arguments (instead of kwargs)

2015-01-22 12:13:17 -08:00

test_server.py

Add + use failure json schema validation

2015-03-11 12:53:15 -07:00

test_types.py

Move to using the oslo.utils stop watch

2015-03-20 17:40:24 -07:00

test_worker.py

Add a test that checks for task result visibility

2015-05-29 17:28:00 -07:00