Conftest fixtures (shared across files) in PyTest - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a fixture in conftest.py that returns a simple string.

PyTest

import pytest

@pytest.fixture
def [1]():
    return "hello"

Drag options to blanks, or click blank then click option'

Agreeting

Bfixture

Ctest_data

Dsetup

Attempts:

3 left

💡 Hint

Common Mistakes

Using invalid Python names for the fixture function.

Forgetting to decorate the function with @pytest.fixture.

The fixture name should be a valid Python function name that describes the data it provides. Here, greeting is a clear and appropriate name.

2fill in blank

medium

Complete the code to use the fixture in a test function in a separate test file.

PyTest

def test_example([1]):
    assert [1] == "hello"

Drag options to blanks, or click blank then click option'

Adata

Bsetup

Cgreeting

Dfixture

Attempts:

3 left

💡 Hint

Common Mistakes

Using a different name than the fixture defined.

Not including the fixture as a parameter in the test function.

The test function receives the fixture name as a parameter to use its returned value. Here, greeting matches the fixture defined in conftest.py.

3fill in blank

hard

Fix the error in the fixture definition to make it shared across multiple test files.

PyTest

import pytest

@pytest.fixture
def [1]():
    return 42

Drag options to blanks, or click blank then click option'

Ashared_fixture

Bfixture

Cdata

Dshared_data

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting the @pytest.fixture decorator.

Naming the fixture inconsistently.

To share a fixture across multiple test files, it must be decorated with @pytest.fixture. The missing decorator causes the fixture not to be recognized.

4fill in blank

hard

Fill both blanks to correctly import pytest and define a fixture that returns a list.

PyTest

[1]

@pytest.fixture
def sample_list():
    return [2]

Drag options to blanks, or click blank then click option'

Aimport pytest

Bimport unittest

C[1, 2, 3]

D(1, 2, 3)

Attempts:

3 left

💡 Hint

Common Mistakes

Using tuple instead of list for the return value.

Importing unittest instead of pytest.

You must import pytest to use its fixture decorator. The fixture returns a list, so the return value should be a list literal.

5fill in blank

hard

Fill all three blanks to define a fixture with scope 'module' and use it in a test function.

PyTest

import pytest

@pytest.fixture(scope=[1])
def config():
    return {"url": "http://example.com"}

def test_url([2]):
    assert [3]["url"] == "http://example.com"

Drag options to blanks, or click blank then click option'

A"module"

Bconfig

D"function"

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect scope string.

Mismatching fixture name in test function parameter.

Using wrong variable name inside the test.

The fixture scope is set to 'module' to share it across tests in the module. The test function receives the fixture named 'config' as a parameter and uses it to assert the URL.

Practice

1. What is the main purpose of placing fixtures in a conftest.py file in pytest?

easy

A. To run tests in parallel automatically

B. To share setup code automatically across multiple test files without importing

C. To store test data in a database

D. To define test cases only for one specific test file

Solution

1. Step 1: Understand the role of conftest.py

   The conftest.py file is used to define fixtures that can be shared across multiple test files without needing explicit imports.

2. Step 2: Identify the purpose of sharing setup code

   Sharing setup code helps avoid repetition and makes tests cleaner and easier to maintain.

3. Final Answer:

   To share setup code automatically across multiple test files without importing -> Option B

4. Quick Check:

   conftest.py shares fixtures automatically [OK]

Hint: Remember: conftest.py shares fixtures without imports [OK]

Common Mistakes:

• Thinking conftest.py runs tests in parallel
• Believing conftest.py stores test data
• Assuming fixtures in conftest.py are for one file only

2. Which of the following is the correct way to define a fixture in conftest.py for sharing across test files?

easy

A. def my_fixture(): return 42

B. class my_fixture: pass

C. @pytest.fixture
def my_fixture(): return 42

D. import pytest
my_fixture = 42

Solution

1. Step 1: Recall fixture syntax in pytest

   Fixtures must be decorated with @pytest.fixture to be recognized by pytest.

2. Step 2: Check each option

   @pytest.fixture def my_fixture(): return 42 correctly uses the decorator and defines a function returning a value. Other options miss the decorator or use wrong syntax.

3. Final Answer:

   @pytest.fixture\ndef my_fixture(): return 42 -> Option C

4. Quick Check:

   Fixtures need @pytest.fixture decorator [OK]

Hint: Always use @pytest.fixture decorator for fixtures [OK]

Common Mistakes:

• Forgetting the @pytest.fixture decorator
• Defining fixtures as classes without decorator
• Assigning fixture values without function

3. Given the following conftest.py fixture and test file, what will be the output when running pytest?

-- conftest.py --
import pytest

@pytest.fixture
def number():
    return 5

-- test_sample.py --

def test_double(number):
    assert number * 2 == 10

def test_triple(number):
    assert number * 3 == 15

medium

A. Both tests pass

B. Both tests fail

C. test_double passes, test_triple fails

D. test_double fails, test_triple passes

Solution

1. Step 1: Understand fixture usage

   The fixture number returns 5 and is shared automatically via conftest.py.

2. Step 2: Evaluate test assertions

   test_double checks 5*2 == 10 (True), test_triple checks 5*3 == 15 (True). Both assertions are correct.

3. Final Answer:

   Both tests pass -> Option A

4. Quick Check:

   Fixture returns 5, assertions match [OK]

Hint: Check fixture value and test assertions carefully [OK]

Common Mistakes:

• Assuming fixture is not shared without import
• Miscalculating expected assertion values
• Confusing test pass/fail logic

4. You have a fixture defined in conftest.py as follows:

import pytest

@pytest.fixture
def data():
    return [1, 2, 3]

In your test file, you wrote:

def test_sum(data):
    assert sum(data) == 10

What is the problem and how to fix it?

medium

A. Assertion is wrong; sum([1,2,3]) is 6, so change 10 to 6

B. Fixture not imported; add from conftest import data

C. Fixture must be a class, not a function

D. sum() cannot be used on lists

Solution

1. Step 1: Check the fixture return value

   The fixture data returns the list [1, 2, 3].

2. Step 2: Calculate the sum and compare with assertion

   sum([1, 2, 3]) equals 6, but the test asserts it equals 10, which is incorrect.

3. Final Answer:

   Assertion is wrong; sum([1,2,3]) is 6, so change 10 to 6 -> Option A

4. Quick Check:

   sum([1,2,3]) = 6, fix assertion [OK]

Hint: Verify expected values match fixture data [OK]

Common Mistakes:

• Thinking fixture must be imported explicitly
• Assuming sum() can't handle lists
• Changing fixture type unnecessarily

5. You want to share a fixture that provides a database connection across multiple test files. You place this fixture in conftest.py:

import pytest

@pytest.fixture(scope="session")
def db_connection():
    conn = create_connection()
    yield conn
    conn.close()

What is the best reason to use scope="session" here?

hard

A. To run tests in parallel using the same connection

B. To create a new connection for every test function

C. To close the connection before each test

D. To create the connection once per test session and reuse it in all tests

Solution

1. Step 1: Understand fixture scopes in pytest

   Scope "session" means the fixture is created once for the entire test run and shared across all tests.

2. Step 2: Apply to database connection use case

   Creating the connection once saves time and resources, and closing it after all tests is efficient.

3. Final Answer:

   To create the connection once per test session and reuse it in all tests -> Option D

4. Quick Check:

   Session scope = one setup per test run [OK]

Hint: Use session scope for expensive setup reused by all tests [OK]

Common Mistakes:

• Thinking session scope creates new instance per test
• Assuming connection closes before each test
• Confusing scope with parallel test execution