Registering markers in pytest.ini - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to register a custom marker named 'slow' in pytest.ini.

PyTest

[pytest]
markers =
    [1]: marks tests as slow

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

Afast

Bslow

Cskip

Dparametrize

Attempts:

3 left

💡 Hint

Common Mistakes

Using a marker name not matching the test decorator.

Leaving the markers section empty.

The marker name 'slow' must be registered exactly as used in tests.

2fill in blank

medium

Complete the code to register two markers 'slow' and 'database' in pytest.ini.

PyTest

[pytest]
markers =
    slow: marks tests as slow
    [1]: marks tests that use the database

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

Adatabase

Bnetwork

Capi

Dui

Attempts:

3 left

💡 Hint

Common Mistakes

Using unrelated marker names.

Misspelling the marker name.

The marker 'database' is used to mark tests that interact with the database.

3fill in blank

hard

Fix the error in the pytest.ini snippet by completing the missing marker name.

PyTest

[pytest]
markers =
    slow: marks tests as slow
    [1] marks tests that require network access

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

Anetwork-

Bnetwork

Cnetwork:

Dnetwork;

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting the colon after the marker name.

Using invalid punctuation.

Each marker must be followed by a colon ':' to describe it properly.

4fill in blank

hard

Fill both blanks to correctly register markers 'slow' and 'api' with descriptions.

PyTest

[pytest]
markers =
    [1]: marks tests as slow
    [2]: marks tests that test the API

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

Aslow

Bfast

Capi

Dui

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing marker names.

Forgetting the colon after marker names.

Markers must be registered with their exact names and a colon before the description.

5fill in blank

hard

Fill all three blanks to register markers 'slow', 'database', and 'network' with descriptions.

PyTest

[pytest]
markers =
    [1]: marks tests as slow
    [2]: marks tests that use the database
    [3]: marks tests that require network access

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

Aslow

Bdatabase

Cnetwork

Dui

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect marker names.

Omitting colons after marker names.

Each marker must be registered with its exact name and a colon before the description.

Practice

1. What is the main purpose of registering markers in the pytest.ini file?

easy

A. To define test data inputs for parameterized tests

B. To organize tests and avoid warnings about unknown markers

C. To automatically generate test reports

D. To speed up test execution by caching results

Solution

1. Step 1: Understand marker registration purpose

   Markers are labels for tests that help organize and select tests to run.

2. Step 2: Recognize why registration is needed

   Registering markers in pytest.ini prevents warnings about unknown markers and keeps tests organized.

3. Final Answer:

   To organize tests and avoid warnings about unknown markers -> Option B

4. Quick Check:

   Marker registration = organize tests + avoid warnings [OK]

Hint: Markers in pytest.ini prevent warnings and organize tests [OK]

Common Mistakes:

• Thinking markers speed up tests
• Confusing markers with test data
• Assuming markers generate reports

2. Which of the following is the correct way to register a marker named slow in pytest.ini?

easy

A. [markers]
slow: marks tests as slow

B. [pytest]
markers = slow

C. [pytest]
slow = marks tests as slow

D. [markers]
slow = marks tests as slow

Solution

1. Step 1: Identify correct section header

   Markers must be registered under the [markers] section in pytest.ini.

2. Step 2: Check syntax for marker registration

   The correct syntax uses an equals sign = with a description, e.g., slow = marks tests as slow.

3. Final Answer:

   [markers] slow = marks tests as slow -> Option D

4. Quick Check:

   Markers section + equals sign = correct syntax [OK]

Hint: Use [markers] section and '=' to register markers [OK]

Common Mistakes:

• Using [pytest] instead of [markers]
• Using colon ':' instead of '='
• Listing markers without description

3. Given this pytest.ini content:

[markers]
api = marks tests as api tests
slow = marks tests as slow

What happens if you run pytest -m slow?

medium

A. Only tests marked with @pytest.mark.slow will run

B. All tests will run except those marked slow

C. Tests marked with @pytest.mark.api will run

D. Pytest will show a warning about unknown marker

Solution

1. Step 1: Understand marker filtering with -m option

   The -m option runs tests matching the given marker name.

2. Step 2: Match marker name with registered markers

   Since slow is registered and used, pytest -m slow runs only tests marked with @pytest.mark.slow.

3. Final Answer:

   Only tests marked with @pytest.mark.slow will run -> Option A

4. Quick Check:

   pytest -m marker = runs tests with that marker [OK]

Hint: pytest -m runs tests with the named marker only [OK]

Common Mistakes:

• Thinking -m excludes tests with the marker
• Confusing marker names
• Expecting warnings when marker is registered

4. You added this to your pytest.ini:

[markers]
fast marks tests as fast

But when running tests, pytest shows a warning about unknown marker 'fast'. What is the problem?

medium

A. Marker name 'fast' is reserved and cannot be used

B. Markers section header is misspelled

C. Missing '=' sign between marker name and description

D. pytest.ini file is in the wrong directory

Solution

1. Step 1: Check marker registration syntax

   The marker line must have an equals sign = between the marker name and its description.

2. Step 2: Identify missing '=' causing warning

   Here, fast marks tests as fast lacks '=', so pytest treats 'fast' as unknown marker.

3. Final Answer:

   Missing '=' sign between marker name and description -> Option C

4. Quick Check:

   Marker line needs '=' sign [OK]

Hint: Always use '=' between marker and description [OK]

Common Mistakes:

• Forgetting '=' sign
• Misspelling [markers] header
• Placing pytest.ini in wrong folder

5. You want to register two markers in pytest.ini: db for database tests and ui for user interface tests. Which pytest.ini content correctly registers both markers?

hard

A. [markers]
db = marks tests as database tests
ui = marks tests as user interface tests

B. [pytest]
markers = db, ui

C. [markers]
db: marks database tests
ui: marks UI tests

D. [pytest]
db = database tests
ui = UI tests

Solution

1. Step 1: Confirm correct section header

   Markers must be under the [markers] section, not [pytest].

2. Step 2: Verify correct syntax for each marker

   Each marker line uses = with a description, e.g., db = marks tests as database tests.

3. Step 3: Check all markers are listed separately

   Both db and ui markers are listed on separate lines with descriptions.

4. Final Answer:

   [markers] db = marks tests as database tests ui = marks tests as user interface tests -> Option A

5. Quick Check:

   Separate lines under [markers] with '=' for each marker [OK]

Hint: List each marker under [markers] with '=' and description [OK]

Common Mistakes:

• Using [pytest] instead of [markers]
• Using commas to list markers
• Using ':' instead of '='