We can do this by using a method that takes args within a fixture and return the method from the fixture. let me show you an example @pytest.fixture def my_fixture(): def _method(a, b): return a*b return _method def test_me(my_fixture): result1 = my_fixture(2, 3) assert result1 == 6 result2 = my_fixture(4, 5) assert result2 == 20
I had the same problem. It is because Werkzeug 3.0.0 was released and Flask doesn’t specify the dependency correctly (requirements says Werkzeug>=2.2.0). This is why, Werkzeug 3.0.0 is still installed and Flask 2.2.2 isn’t made for Werkzeug 3.0.0. Solution: Just set a fix version for Werkzeug such as Werkzeug==2.2.2 in your requirements.txt and it should … Read more
This is actually supported natively in py.test via indirect parametrization. In your case, you would have: @pytest.fixture def tester(request): “””Create tester object””” return MyTester(request.param) class TestIt: @pytest.mark.parametrize(‘tester’, [[‘var1’, ‘var2’]], indirect=True) def test_tc1(self, tester): tester.dothis() assert 1
I’m not sure why py.test does not add the current directory in the PYTHONPATH itself, but here’s a workaround (to be executed from the root of your repository): python -m pytest tests/ It works because Python adds the current directory in the PYTHONPATH for you.
By default, py.test captures the result of standard out so that it can control how it prints it out. If it didn’t do this, it would spew out a lot of text without the context of what test printed that text. However, if a test fails, it will include a section in the resulting report … Read more
Is this the correct use of conftest.py? Yes it is. Fixtures are a potential and common use of conftest.py. The fixtures that you will define will be shared among all tests in your test suite. However, defining fixtures in the root conftest.py might be useless and it would slow down testing if such fixtures are … Read more
You can use -k option to run test cases with different patterns: py.test tests_directory/foo.py tests_directory/bar.py -k ‘test_001 or test_some_other_test’ This will run test cases with name test_001 and test_some_other_test deselecting the rest of the test cases. Note: This will select any test case starting with test_001 or test_some_other_test. For example, if you have test case … Read more
pytest.raises(Exception) is what you need. Code import pytest def test_passes(): with pytest.raises(Exception) as e_info: x = 1 / 0 def test_passes_without_info(): with pytest.raises(Exception): x = 1 / 0 def test_fails(): with pytest.raises(Exception) as e_info: x = 1 / 1 def test_fails_without_info(): with pytest.raises(Exception): x = 1 / 1 # Don’t do this. Assertions are caught … Read more
The -s switch disables per-test capturing (only if a test fails). -s is equivalent to –capture=no.
The problem is that when the worker returns the scope of “with” statement ends making the object take its real value, the solution is to use “yield”. @pytest.fixture() def mocked_worker(): with patch(‘test.test_module.os.getcwd’, return_value=”Testing”): result = Worker() yield result