tests: run Test_django_db_blocker in testdir

[blueyed]

Ref: #802 (comment)

[SalmonMode]

Placing them in a subprocess fix the issue that django_db_blocker currently has. WHen django_db_blocker is requested on its own, the DB is not set up. These tests pass because of the other two tests that trigger the session scope-level django_db_setup fixture. Because they always run first (due to the test reordering logic), the DB will always be prepared for the other two tests (that would fail if run on their own).

The fix I found was to rename django_db_blocker to _django_db_blocker, have django_db_setup use that, and then create a new session scope-level fixture called django_db_blocker which requests both of them. This way, whenever django_db_blocker is called, it ensures the DB is set up.

[blueyed]

@SalmonMode thanks!
Do you want to create a PR for this (in case you have it ready already locally)?
Otherwise I'll do so later.

I think this PR/change still makes sense (separately), since it simulates running the tests alone. And it could be extended then to test what your renaming/re-arranging would fix (in a separate test).

[SalmonMode]

I'd be happy to 😁

There's some already existing tests I can make tweaked copies of to cover this.

Sorry for causing all the ruckus, btw.

[blueyed]

I'd be happy to

Great. I assume this can be done on top of this one?
I.e. run pytest also with selecting only a single test (not using the db) from it.

There's some already existing tests I can make tweaked copies of to cover this.

I'd rather avoid new tests if existing ones can be extended / hardened - the test suite is rather slow already, especially due to all the runpytest_subprocess tests.

Sorry for causing all the ruckus, btw.

No worries.. :)

[SalmonMode]

I'd rather avoid new tests if existing ones can be extended / hardened - the test suite is rather slow already, especially due to all the runpytest_subprocess tests.

Not a problem. I can just tweak them in place.

I assume this can be done on top of this one?
I.e. run pytest also with selecting only a single test (not using the db) from it.

Sorry, I'm not sure I follow. You mean if I can make changes on top of the current change you're making here?

[SalmonMode]

Here's the PR #807