| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
Overlord() api class. It will catch them, and then marshall them into
a dict of {'name':"?", 'error':1, 'message':"?". 'info':{dict of whatever}}
It will also exit the process with status 1 instead of 0.
Also, some refactoring to make the error handling a little easier.
|
| |
|
|
| |
group related things
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
The groups weren't getting seperated correctly (they expected a ':' as the
seperator, which is wrong).
Uncomment some of the test cases for this that now work.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
add support for testing yaml/json input/output
add support for async testing of all tests
try `nosetests -a async test_func_transmit.py` to test all the async test
try `nosetest -a json test_func_transmit.py` to test all the json tests, etc
NOTE: several of these tests fail for json/yaml, not sure what to do about that
|
| |
|
|
|
|
|
| |
approach, but it seems to mostly work for now
test_func_transmit.py:
more test cases for func-transmit
|
|
|
unit tests for func-transmit
right now, mostly just tests of marshalling data back and forth properly, and some basic calls
NOTE: at the moment, it fails alot of these tests
test_clients.py:
add a couple new tests based on things discovered with test_func_transmit.py
|
