That moment when you kick off pytest
& everything runs correctly on the first try.

My manager asked me why unitary tests are important.

Just spent two hours figuring out why some tests did not run correctly.

FYI: if you’re using pytest, do not forget the ‘s’ at the end of the usefixtures decorator.

@pytest.mark.usefixtures(‘session’)
class TestFoo:
pass

I feel so dumb!

Fucking test, son of a bug I made you finally green. Test Driven Data Science induced RAGE.

Anyone using nose2 as their primary unit testing framework?

If so, why do you prefer it over pytest? The nose2 homepage effective recommends pytest, so wondering about the future of nose2.

Scenario: Enabling yet another python test suite on vscode. No big deal.

I start the test init and discovery. Says it cant find the test files. Okay; usually the issue is there's no __init__.py in the test directory. It's okay we can fix that.

Oh wait it's still not working. Okay well this isnt good... After about an hour of searching, i finally find out that the file that vscode is discovering tests with doesnt exist... In fact the whole testing directory doesnt exist!

Okay so now what do i do... Reinstall? Doesnt work. Reinstall and delete the extension directory? Yes! Victory!

Dont know how i got a half-baked extension download but hey... Could've beem worse.

Pytest are doom for the society.

If there existed a framework like pytest for other languages, would you use it?

If that framework made those tests part of the documentation to show how the system works, would you be more likely to?

Why can't you put periods on the end of your docstrings!?

Working on a portfolio project - I ran some tests, everything is all good - 100% passing. Computer freezes - pop_os has been giving me shit lately, so I have to restart. Fine.

I get back into code, i re-run pytest - nothing works. Python apparently can't find my modules anymore. I try a few things, nothing. Why? Who the fuck knows - "oh you need this conftest file", "oh you need to remove __init__ from this directory or that one", "oh it's a pytest version iss---" no, no, no - listen here you little shit, it was working two seconds ago. Tell me why and how software I wrote with the most basic ass package structure - literally TWO directories suddenly has no fucking clue how to import the modules. hmm? Even from within the app directory, app.server now no longer recognizes imports from app.main or app.database.

ALL of this worked. It works in new directories without dedicated venvs - it works in new directories with my global python install - it works with any one of my conda envs - it works on other computers - WHY doesn't it work in THIS directory all of a sudden?? Ugh.

What's terrible is that relative imports will probably solve it within the app dir, but the tests dir won't accept them. Moreover, vs code autocompletion can find all the modules, but python itself cannot. Fucking infuriating shit like this is.