如何将Pytest Fixture作为测试类属性而非方法参数使用？

Absolutely, repeating fixture names in every test method signature is tedious and breaks the DRY principle. Good news—you can absolutely make fixtures accessible as test class attributes, so you only set them up once and use self.fixture_name in all your methods. Here's how to do it:

Step 1: Adjust Your Fixture Scope (Optional but Recommended) #

First, if your fixture is used across multiple tests in a class, set its scope to class to avoid redundant work (like re-fetching the Google page for every test). This is optional but improves performance:

from bs4 import BeautifulSoup
import pytest
import requests

@pytest.fixture(scope="class")
def google():
    # This runs once per test class, not per method
    response = requests.get("https://google.com")
    return BeautifulSoup(response.text, "html.parser")

Step 2: Create a Setup Fixture to Attach the Fixture to the Class #

Next, make a helper fixture that uses pytest's request object to assign the google fixture to your test class as an attribute. Use autouse=True so this setup runs automatically for all tests in the class:

@pytest.fixture(autouse=True, scope="class")
def attach_google_fixture(request, google):
    # Assign the google fixture to the test class instance
    request.cls.google = google

Step 3: Use the Fixture as a Class Attribute in Tests #

Now, your test class no longer needs to include google in every method signature. Just access it via self.google:

class TestGoogle:
    def test_page_title(self):
        assert "Google" in self.google.title.string
    
    def test_search_box_exists(self):
        search_box = self.google.find("input", {"name": "q"})
        assert search_box is not None
        assert search_box.has_attr("type") and search_box["type"] == "text"
    
    def test_footer_links(self):
        footer = self.google.find("footer")
        assert footer is not None
        assert len(footer.find_all("a")) > 0

Key Explanations: #

• autouse=True: Ensures this setup fixture runs automatically for all tests in the class—no need to explicitly reference it.
• scope="class": Matches the scope of your google fixture, so the setup runs once per class (not per test method).
• request.cls: Gives access to the test class instance, allowing you to attach the fixture as an attribute that all methods can access via self.

Alternative: Inherit from a Base Test Class #

If you want to reuse this pattern across multiple test classes, create a base class with the setup logic and inherit from it:

class BaseWebTest:
    @pytest.fixture(autouse=True, scope="class")
    def setup_web_fixtures(self, request, google):
        request.cls.google = google

class TestGoogle(BaseWebTest):
    def test_title(self):
        assert "Google" in self.google.title.string

class TestGoogleSearch(BaseWebTest):
    def test_search_button(self):
        assert self.google.find("input", {"name": "btnK"}) is not None

This keeps your code even drier by centralizing the fixture attachment logic.

Important Notes: #

• Make sure your fixture scopes align: If your main fixture (like google) is function-scoped, your setup fixture should also be function-scoped (though class-scoped is better for performance when possible).
• If you have multiple fixtures to attach, just add them to the setup fixture's parameters and assign them all to request.cls:

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

内容的提问来源于stack exchange，提问作者Donal