PyTest vs unittest vs nose comparison - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Key difference in test discovery between PyTest and unittest

Which statement correctly describes how PyTest and unittest discover tests?

A PyTest automatically finds tests by looking for files and functions starting with 'test', while unittest requires explicit test suites or naming conventions.

B Both PyTest and unittest require manual registration of tests in a suite to run them.

C unittest automatically finds tests by looking for files and functions starting with 'test', while PyTest requires explicit test suites or naming conventions.

D Neither PyTest nor unittest supports automatic test discovery.

💡 Hint

Think about which framework is known for simpler test discovery without extra setup.

PyTest automatically discovers tests by scanning files and functions starting with 'test'. unittest can discover tests but often requires defining test suites or following strict naming conventions.

❓ Predict Output

intermediate

Output difference when a test fails in PyTest vs unittest

Given the following test code, what is the main difference in output when the assertion fails in PyTest compared to unittest?

PyTest

def test_example():
    assert 1 == 2

import unittest
class TestExample(unittest.TestCase):
    def test_example(self):
        self.assertEqual(1, 2)

A unittest shows a detailed assertion failure with values, PyTest shows a simple failure message.

B Both show identical assertion failure messages.

C Neither shows any assertion failure message.

D PyTest shows a detailed assertion failure with values, unittest shows a simple failure message.

💡 Hint

Consider which framework provides more readable failure details by default.

PyTest enhances assertion introspection, showing exact values and differences on failure. unittest shows a more basic failure message unless customized.

❓ locator

advanced

Best locator strategy for selecting a test function in PyTest

In PyTest, which locator is the best practice to select and run a specific test function named test_login_valid inside test_auth.py?

A pytest -k test_login_valid

B pytest test_auth.py::test_login_valid

C pytest test_auth.py -m test_login_valid

D pytest --select test_login_valid

💡 Hint

Think about the syntax to run a specific test function in a file.

The syntax pytest filename::test_function runs the specific test function. Option B runs tests matching the keyword but may run multiple tests.

❓ assertion

advanced

Which assertion style is valid in unittest but invalid in PyTest?

Which assertion statement is valid in unittest but will cause an error in PyTest?

A self.assertTrue(a == b)

B assert a == b

C self.assertEqual(a, b)

D assertEqual(a, b)

💡 Hint

Consider which assertion methods require a class instance.

unittest assertions like self.assertEqual() require a TestCase class instance. PyTest uses plain assert statements and does not support self.assertEqual() outside classes.

❓ framework

expert

Choosing the best framework for legacy test suites with complex setup

You have a large legacy Python project with many tests using unittest.TestCase classes and complex setup/teardown methods. You want to gradually migrate to a more modern testing framework without rewriting all tests at once. Which framework is the best choice?

A Use PyTest, as it supports running unittest tests and allows gradual migration with fixtures.

B Switch immediately to nose, as it is designed for legacy unittest compatibility and modern features.

C Rewrite all tests to pure PyTest style before running any tests to avoid compatibility issues.

D Use unittest only, as mixing frameworks causes test failures.

💡 Hint

Consider which framework supports running existing unittest tests without rewriting.

PyTest can run unittest.TestCase tests without changes and supports fixtures for new tests, enabling gradual migration. nose is outdated and less maintained. Rewriting all tests at once is risky and time-consuming.