In this case, pytest-warnings are warnings which were generated for pytest and/or it’s plugins. These warnings were not generated for your code. In order to list them in the report, you will need to use option -r w. Here is portion of py.test –help: -r chars show extra test summary info as specified by chars … Read more
TLDR: I suspect you installed pytest within your system level python site-packages so when you try to run pytest, within your virtualenv, it’s throwing a ModuleNotFoundError since it doesn’t have this dependency installed within your virtualenv. Virtual environments give you a sandboxed environment so you can experiment with potential python libraries for your project, but … Read more
If you subclass from unittest.TestCase, your test methods cannot have additional arguments. If you simply subclass from object, it will work (though you’ll have to use regular assert statements instead of the TestCase.assertEqual methods. import unittest import pytest class TestCase(object): @pytest.mark.parametrize(“test_input,expected”, [ (“3+5”, 8), (“2+4”, 6), (“6*9”, 42), ]) def test_1(self, a, b): assert eval(a) … Read more
Pass the exceptions as a tuple to raises: with pytest.raises( (MachineError, NotImplementedError) ): verb = … In the source for pytest, pytest.raises may: catch expected_exception; or pass expected_exception to a RaisesContext instance, which then uses issubclass to check whether the exception was one you wanted. In Python 3, except statements can take a tuple of … Read more
The OP’s requirement was for setup and teardown each to execute only once, not one time per module. This can be accomplished with a combination of a conftest.py file, @pytest.fixture(scope=”session”) and passing the fixture name to each test function. These are described in the Pytest fixtures documentation Here’s an example: conftest.py import pytest @pytest.fixture(scope=”session”) def … Read more
My approach would probably to create a fixture which can generate your objects: @pytest.fixture def thing(request, db): class ThingFactory(object): def get(self): thing = MyModel.objects.create() request.addfinalizer(thing.delete) return thing return ThingFactory() def test_thing(thing): thing1 = thing.get() thing2 = thing.get() Obviously you can make .get() take an argument etc. (PS: Also note there’s no need for the lambda … Read more
I found: def pytest_sessionfinish(session, exitstatus): “”” whole test run finishes. “”” exitstatus can be used to define which action to run. pytest docs about this
Try –log-cli-level=INFO like: pytest -vv -s –log-cli-level=INFO –log-cli-format=”%(asctime)s [%(levelname)8s] %(message)s (%(filename)s:%(lineno)s)” –log-cli-date-format=”%Y-%m-%d %H:%M:%S” ./test_file.py
I know this question has been already closed, but a simple way I often use is to call pytest via python -m, from the root (the parent of the package). $ python -m pytest tests This works because -m option adds the current directory to the python path, and hence mypkg is detected as a … Read more
You should use the warning filters options (ini or marks): [pytest] filterwarnings = ignore::DeprecationWarning:botocore.*: Source: https://docs.python.org/3/library/warnings.html#default-warning-filter “Individual warnings filters are specified as a sequence of fields separated by colons:” action:message:category:module:line