Strange behaviour with Pytest when running script is imported as module in another test file. about pytest-console-scripts HOT 4 CLOSED

No worries, it happens. BTW, if you have further problems with mocking in the scripts you might want to check out this issue #44 -- the discussion there and the linked stackoverflow thread clarify some issues related to mocking and scripts.

Funny enough, I had no problem with this one cause I got there straight from readme)
Now everything is working with mocks and imports. Big thanks for this tool!

from pytest-console-scripts.

I see two things here:

1. test_import_my_script.py doesn't mock anything.
2. More importantly, the prints in mock_check.my_script are executed when it is imported, which is before any tests are executed or any fixtures are created. Even if there was mocking, it would not be in effect yet.

I think the behavior that you observe is exactly how it should be. The content of sys.argv is also correct. It's the sys.argv of the pytest process (which imports mock_check.my_script where that print is located via test_import_my_script.py), so it contains the path to pytest.

To summarize: mocking only applies while the mocking fixture is in effect, which is inside of test_mock_check. For the rest of the time requests.get is the original one and it can't get "fake.url".

Does this make sense?

from pytest-console-scripts.

Well, thanks for pointing out the import issue. I tried to simplify the example and renamed my_scrip.py. Originally it was main.py and contained some code not wrapped into if __name__ == "__main__". While I've been blaming the mocking, the problem was that I looked right trough this unwrapped code. 🤦‍♂️ Sorry for the bustle.

from pytest-console-scripts.

No worries, it happens. BTW, if you have further problems with mocking in the scripts you might want to check out this issue #44 -- the discussion there and the linked stackoverflow thread clarify some issues related to mocking and scripts.

from pytest-console-scripts.