In unittest, I can setUp variables in a class and then the methods of this class can chose whichever variable it wants to use…
class test_class(unittest.TestCase):
def setUp(self):
self.varA = 1
self.varB = 2
self.varC = 3
self.modified_varA = 2
def test_1(self):
do_something_with_self.var….
I’m trying to test if one of my variables is pd.NaT. I know it is NaT, and still it won’t pass the test. As an example, the following code prints nothing :
a=pd.NaT
if a == pd.NaT:
print(“a not NaT”)
Does anyone have a clue ? Is there a way to effectively test if a is NaT?
….
I have a Python 2.7 method that sometimes calls
sys.exit(1)
Is it possible to make a unit test that verifies this line of code is called when the right conditions are met?
….
Can anyone explain the use of Python’s setUp and tearDown methods while writing test cases apart from that setUp is called immediately before calling the test method and tearDown is called immediately after it has been called?
….
How do you mock a readonly property with mock?
I tried:
setattr(obj.__class__, ‘property_to_be_mocked’, mock.Mock())
but the issue is that it then applies to all instances of the class… which breaks my tests.
Do you have any other idea? I don’t want to mock the full object, only this specific property.
….
Is it possible to mock a return value of a function called within another function I am trying to test? I would like the mocked method (which will be called in many methods I’m testing) to returned my specified variables each time it is called. For example:
class Foo:
def method_1():
results = uses_some_other_method()
def method_n(….
Suppose I have the following code in a Python unit test:
aw = aps.Request(“nv1”)
aw2 = aps.Request(“nv2”, aw)
Is there an easy way to assert that a particular method (in my case aw.Clear()) was called during the second line of the test? e.g. is there something like this:
#pseudocode:
assertMethodIsCalled(aw.Clear, lambda: aps.Request(“nv2”, aw))
….
My Django unit tests take a long time to run, so I’m looking for ways to speed that up. I’m considering installing an SSD, but I know that has its downsides too. Of course, there are things I could do with my code, but I’m looking for a structural fix. Even running a single test is slow since the database needs to be rebuilt / south migrated every….
The Celery documentation mentions testing Celery within Django but doesn’t explain how to test a Celery task if you are not using Django. How do you do this?
….
I tried to use the norecursedirs option inside setup.cfg to tell py.test not to collect tests from certain directories but it seems it does ignore it.
[tool:pytest]
norecursedirs=lib/third
When I run py.test I do see how it does get tests from inside lib/third!
….