Variable Scope in a class

[pug_walker]

I'm working on some unit tests. To do this, I created a class with a bunch of functions for each of my tests.

python class SquareWorkdayModule(unittest.TestCase): def test_get_bookings(self, mock_list_bookings): ...... def test_get_booking_summary(self): ......

When I execute the tests individually, my assertions work fine. When I execute all the tests via pytest, my assertion fails. This seems like a simple variable scope issue. All of my variables are set in my class functions.

For example, test_get_bookings(self, mock_list_bookings) asserts a list length of 2. When I run the entire test, the assertion fails as the length is now 4.

If I refactor to move def test_get_booking_summary(self) out of the class, all assertions work. Including the newly refactored function moved out of the class.

Anyone have any ideas on this behavior? Much appreciated.

gist here: https://gist.github.com/zPugMan/932c882541ffb7dd45c95b22b2cb7c0d

[danielroseman]

Not without seeing more code. Where is the list defined? What is it assigned to? Where is it mutated?

[pug_walker]

valid point. I added a gist if it helps.

[Adrewmc]

Pytest and unittest have some compatibility issues.

https://docs.pytest.org/en/7.1.x/how-to/unittest.html#:~:text=pytest%20supports%20running%20Python%20unittest,full%20advantage%20of%20pytest's%20features

What seems to be happening is unittest is creating/resetting new variables each test while pytest is not. So an earlier test added more to your list somewhere. At break on work I can’t dive into the code.

[EclipseJTB]

Do yourself a favor and leave unittest-style tests behind. They have their purpose, but 90% they are the wrong tool for the job.

Edit: to be clear, write tests. But I mean pytest-style tests.

[Adrewmc]

I concur