Solution: import pytest @pytest.mark.django_db class TestExample: def test_one(): … Assume that you’ve created a TestExample class inside your test file and it should be decorated with @pytest.mark.django_db. It should solve your problem.
I think you also need to specify the directory/file you want coverage for like py.test –cov=MYPKG –cov-report=html after which a html/index.html is generated.
pytest does not provide an assertCountEqual, but we can just use unittest’s: import unittest def test_stuff(): case = unittest.TestCase() a = [{‘a’: 1}, {‘b’: 2}] b = [{‘b’: 2}] case.assertCountEqual(a, b) And the output is decent, too $ py.test ============================= test session starts ============================== platform linux — Python 3.6.2, pytest-3.2.1, py-1.4.34, pluggy-0.4.0 rootdir: /home/they4kman/.virtualenvs/tmp-6626234b42fb350/src, inifile: … Read more
I encountered the same issue when calling “py.test –cov …” from tox. I found a hint on this page: http://blog.ionelmc.ro/2014/05/25/python-packaging/ even though it does not mention this explicitly. Using “–develop” for tox will make sure that coverage data gathering is called from the same directory as coverage analysis. This section in tox.ini made it work … Read more
Starting with VSCode 1.59 and the new Testing API (?) there are now these two new commands: Run Test at Cursor Debug Test at Cursor
I had to put the register_assert_rewrite into tests/__init__.py like so: import pytest # we want to have pytest assert introspection in the helpers pytest.register_assert_rewrite(‘tests.helpers’)
You need to run poetry install to set up your dev environment. It will install all package and development requirements, and once that is done it will do a dev-install of your source code. You only need to run it once, code changes will propagate directly and do not require running the install again. If … Read more
For sharing data between tests, you could use the pytest namespace or cache. Namespace Example with sharing data via namespace. Declare the shared variable via hook in conftest.py: # conftest.py import pytest def pytest_namespace(): return {‘shared’: None} Now access and redefine it in tests: import pytest def test_creation(): pytest.shared = ‘spam’ assert True def test_deletion(): … Read more
This works for me, please try: import asyncio import pytest pytest_plugins = (‘pytest_asyncio’,) @pytest.mark.asyncio async def test_simple(): await asyncio.sleep(0.5) Output of pytest -v confirms it passes: collected 1 item test_async.py::test_simple PASSED And I have installed: pytest 6.2.5 pytest-asyncio 0.16.0 # anyio not installed
The db fixture has the function scope for a reason, so the transaction rollbacks on the end of each test ensure the database is left in the same state it has when test starts. Nevertheless, you can have the session/module scoped access to database in fixture by using the django_db_blocker fixture: @pytest.fixture(scope=”module”) def get_all_models(django_db_blocker): with … Read more