Both Pytest Fixtures and regular functions can be used to structure to test code and reduce code duplication. The answer provided by George Udosen does an excellent job explaining that. However, the OP specifically asked about the differences between a pytest.fixture and a regular Python function and there is a number of differences: Pytest Fixtures … Read more
Could be something similar to this. Run it with: python manage.py dumpdata –indent=2 -v 2 –traceback gigs To see the underlying error.
I was also looking for this one and as I was researching I’ve stumbled on a lot of code and did pieced them all together (I wish there were better documents though) but here’s my part of the code. Address is a 1..1 relationship and Phones is a 1..n relationship to events. factory :event do … Read more
Instead of assertions in the setup to check the result, I used a simple test (a test method along the others, but positionned as first test method). I have seen several advantages: The setup keeps short and focused, for readability. The assertions are run only once, which is more efficient. Usage and discussion : For … Read more
The only difference is in readability. I think (though I’m not 100% sure) the underlying behavior is identical (i.e. the cleanup after the yield statement is run as a finalizer). I always prefer using yield fixtures for cleanup, since it’s more readable. If you’re using pytest <3.0, you’ll still need to use pytest.yield_fixture to get … Read more
Just FYI, you can also use the initialize_with macro inside your factory and check to see if the object already exists, then don’t create it over again. The solution using a lambda (its awesome, but!) is replicating logic already present in find_or_create_by. This also works for associations where the :league is being created through an … Read more
py.test will import conftest.py and all Python files that match the python_files pattern, by default test_*.py. If you have a test fixture, you need to include or import it from conftest.py or from the test files that depend on it: from sonoftest import pytest_addoption, cmdopt
You should be able to load your fixtures prior to entering console. Like this: RAILS_ENV=test bin/rails db:fixtures:load RAILS_ENV=test bin/rails console However, you still won’t be able to access your fixture data like you would in a test. This simply loads your test database with your fixtures data. So you’d still have to do something like: … Read more
The easiest way to control the order in which fixtures are executed, is to just request the previous fixture in the later fixture. So to make sure b runs before a: @pytest.fixture(autouse=True, scope=”function”) def b(): pass @pytest.fixture(scope=”function”) def a(b): pass For details on the general fixture resolution order, see Maxim’s excellent answer below or have … Read more
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