Andreas Pelme
Andreas Pelme
I had a bunch of tests that I was not too proud of (some tests that inherited a huge Unittest base class with huge/inflexible setUp of heavy database objects). I...
This is a very useful addition which I planned to add too. I am now using this code in production and it seems to work fine!
👍 We (@blueyed and me) discussed this during the pytest sprint. I forgot about it when reviewing the mailoutbox fixture. :/ Keeping aliases for quite some time and emit pytest...
This is something I personally have been thinking about and wanting for a long time. The API and implementation looks good and simple to use! Passing request explicitly to tie...
@ktosiek It is possible to test that with a "pytester" test, that invokes a new pytest session. See for instance https://github.com/pytest-dev/pytest-django/blob/f1711f01c894682b69fed1924676916ecea53fb1/tests/test_unittest.py#L122-L153. The trick is to use the `django_testdir` fixture which...
Hmm, couldn't we monkey patch _post_teardown in those cases and have it not close the connection? It would for sure be nice to support Django 1.6 and 1.7 if possible!
@aaugustin Agreed, it wouldn't be too bad to not support Django
/cc @nicoddemus 😅
Sorry, doctests and pytest fixtures (which is used to get the database ready for use) does not really play well together. The error message is misleading, but doing database operations...
@ssangervasi can you please open a separate issue for the import syntax error? @adamchainz I think it should be enabled by default, it seems useful and nice to follow Django's...