caliendo
caliendo copied to clipboard
buzzfeed
caliendo
for example, functions that are wrapped with a celery `@task` decorator currently cannot be stubbed out by caliendo
Given you have a particular feature in `foo_bar.py` that you need to test, you will write a `unittest.TestCase` subclass and several methods that test the different use cases your feature...
Given that you call `caliendo.expected_value.is_equal_to` with any given value, when you call it again with the exact same value and from the same place so that the stack trace remains...
When the environment variable, CALIENDO_DISABLE_COUNTER is set to 'True' disable the counter such that it always returns 0
How to reproduce: given that we have one of the following scenarios ``` def foo(): # do something ``` or ``` class MyTestCase(unittest.TestCase): def foo(self): # do something ``` if...
tests need to be broken out and organized better by functionality
Would be cool if there were a caliendo decorator that caused a test to run in multiprocessiing mode.
If a method isn't defined on a class directly it can't be stubbed out. Add support for this by wrapping getattr on the parent class (or with some other mechanism)
Create a decorator that can be passed a function handle which then watches the handle (by wrapping it) in the context of a patch. Each time the function is called...