Pytest fixture for a class through self not as method argument

by

Sure, just use an autouse fixture. Here is the relevant spot in pytest docs. In your example, the change would be introducing an extra fixture (I named it _request_google_page):

from bs4 import BeautifulSoup
import pytest
import requests

@pytest.fixture()
def google():
    return requests.get("https://www.google.com")


class TestGoogle:

    @pytest.fixture(autouse=True)
    def _request_google_page(self, google):
        self._response = google

    def test_alive(self):
        assert self._response.status_code == 200

    def test_html_title(self):
        soup = BeautifulSoup(self._response.content, "html.parser")
        assert soup.title.text.upper() == "GOOGLE"

You could even drop the google fixture completely and move the code to _request_google_page:

@pytest.fixture(autouse=True)
def _request_google_page(self):
    self._response = requests.get("https://www.google.com")

Note that _request_google_page will be called once per test by default, so each test will get a new response. If you want the response to be initialized once and reused throughout all tests in the TestGoogle class, adjust the fixture scopes (scope="class" for _request_google_page and scope="module" or scope="session" for google). Example:

from bs4 import BeautifulSoup
import pytest
import requests


@pytest.fixture(scope="module")
def google():
    return requests.get("https://www.google.com")


@pytest.fixture(autouse=True, scope="class")
def _request_google_page(request, google):
    request.cls._response = google


class TestGoogle:

    def test_alive(self):
        assert self._response.status_code == 200

    def test_html_title(self):
        soup = BeautifulSoup(self._response.content, "html.parser")
        assert soup.title.text.upper() == "GOOGLE"

More Related Contents:

  1. PATH issue with pytest ‘ImportError: No module named YadaYadaYada’
  2. How to properly assert that an exception gets raised in pytest?
  3. How to test a function with input call?
  4. how to share a variable across modules for all tests in py.test
  5. How to mock a readonly property with mock?
  6. How do you generate dynamic (parameterized) unit tests in Python?
  7. How do I run all Python unit tests in a directory?
  8. How unique is Python’s id()?
  9. How do you write tests for the argparse portion of a python module?
  10. Python unittest.TestCase execution order
  11. Where do the Python unit tests go? [closed]
  12. How to parametrize a Pytest fixture
  13. How to supply stdin, files and environment variable inputs to Python unit tests?
  14. Python mock multiple return values
  15. How can I see normal print output created during pytest run?
  16. Mocking a class: Mock() or patch()?
  17. Python: Write unittest for console print
  18. Assert that a method was called in a Python unit test
  19. Mock attributes in Python mock?
  20. Access self from decorator
  21. Python unittest – opposite of assertRaises?
  22. Is there a way to specify which pytest tests to run from a file?
  23. What is the difference between setUp() and setUpClass() in Python unittest?
  24. Outputting data from unit test in Python
  25. How can I limit the maximum running time for a unit test?
  26. PyCharm noinspection for whole file?
  27. Pass a Python unittest if an exception isn’t raised
  28. pydev breakpoints not working
  29. How can I specify a database for Django Tests to use instead of having it build it every time?
  30. Can I “fake” a package (or at least a module) in python for testing purposes?

Leave a Comment