Why plugins extend PyTest capabilities - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use plugins in PyTest?

Which of the following best explains why plugins are used to extend PyTest capabilities?

A Plugins add new features and hooks to customize test runs without changing PyTest core.

B Plugins replace PyTest core to run tests faster by skipping setup steps.

C Plugins are used to write tests in different programming languages inside PyTest.

D Plugins automatically fix failing tests by rewriting test code.

💡 Hint

Think about how plugins help without modifying the main tool.

Plugins allow adding features and hooks to PyTest, enabling customization and integration without altering PyTest's core code.

❓ Predict Output

intermediate

Output of PyTest with a plugin hook

What will be the output when running this PyTest test with a plugin that implements pytest_runtest_setup hook printing 'Setup called'?

PyTest

def test_example():
    assert True

A

Setup called
.
1 passed

B

.
Setup called
1 passed

C

1 passed
Setup called

D

Setup called
1 failed

💡 Hint

The setup hook runs before the test and prints first.

The pytest_runtest_setup hook runs before the test and prints 'Setup called'. Then the test runs and passes, showing '.' and '1 passed'.

❓ assertion

advanced

Correct assertion for plugin-added marker

Given a PyTest plugin adds a marker 'slow' to tests, which assertion correctly checks if a test has this marker?

PyTest

def test_has_marker(request):
    # Check if 'slow' marker is present
    pass

A assert request.node.has_marker('slow')

B assert 'slow' in request.node.keywords

C assert request.node.get_closest_marker('slow') is not None

D assert request.node.marker('slow') == True

💡 Hint

Use the official PyTest API to get markers.

The correct way is to use get_closest_marker which returns the marker object or None if not found.

🔧 Debug

advanced

Debugging plugin import error in PyTest

A PyTest plugin fails to load with error: ModuleNotFoundError: No module named 'pytest_custom'. What is the most likely cause?

A The test function is missing the @pytest.mark decorator.

B The test file name does not start with 'test_'.

C PyTest version is too new and does not support plugins.

D The plugin package 'pytest_custom' is not installed in the environment.

💡 Hint

ModuleNotFoundError means Python cannot find the module.

This error means the plugin package is missing or not installed in the current Python environment.

❓ framework

expert

How plugins affect PyTest test discovery

Which statement correctly describes how PyTest plugins can influence test discovery?

A Plugins only affect test execution, not discovery.

B Plugins can add custom hooks to modify or filter which files and tests PyTest discovers and runs.

C Plugins disable PyTest's built-in test discovery and require manual test listing.

D Plugins force PyTest to discover tests only in the current directory.

💡 Hint

Think about how plugins can change PyTest behavior before tests run.

Plugins can implement hooks like pytest_collect_file to customize test discovery, filtering, or adding new test sources.