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.

Practice

1. Which testing framework is built into Python and uses classes for organizing tests?

easy

A. doctest

B. pytest

C. nose

D. unittest

Solution

1. Step 1: Recall built-in Python testing frameworks

   Python's standard library includes unittest as the built-in testing framework.

2. Step 2: Identify framework structure

   unittest organizes tests using classes, unlike pytest which uses functions.

3. Final Answer:

   unittest -> Option D

4. Quick Check:

   Built-in + classes = unittest [OK]

Hint: Built-in and class-based means unittest [OK]

Common Mistakes:

• Confusing pytest as built-in
• Thinking nose is built-in
• Mixing doctest with unittest

2. Which of the following is the correct way to write a simple test function in pytest?

easy

A. def example_test(): assert 1 == 1

B. class TestExample(unittest.TestCase): def test_example(self): assert 1 == 1

C. def test_example(): assert 1 == 1

D. def testExample(): assert 1 == 1

Solution

1. Step 1: Identify pytest test function naming

   pytest requires test functions to start with 'test_' to be auto-discovered.

2. Step 2: Check syntax correctness

   def test_example(): assert 1 == 1 defines a function named 'test_example' with a valid assertion, matching pytest style.

3. Final Answer:

   def test_example(): assert 1 == 1 -> Option C

4. Quick Check:

   Function name starts with test_ for pytest [OK]

Hint: Test functions start with 'test_' in pytest [OK]

Common Mistakes:

• Using class-based tests in pytest by default
• Naming test functions without 'test_' prefix
• Using camelCase instead of snake_case

3. Given the following code, what will pytest output when running this test?

def test_sum():
    assert sum([1, 2, 3]) == 6
    assert sum([1, 2, 3]) == 7

medium

A. Test passes successfully

B. Test fails on second assertion

C. Syntax error due to assert statements

D. Test skipped automatically

Solution

1. Step 1: Analyze first assertion

   sum([1, 2, 3]) equals 6, so first assertion passes.

2. Step 2: Analyze second assertion

   sum([1, 2, 3]) is 6, but assertion expects 7, so it fails.

3. Final Answer:

   Test fails on second assertion -> Option B

4. Quick Check:

   Second assert false causes failure [OK]

Hint: Check each assert; failure stops test [OK]

Common Mistakes:

• Assuming all asserts pass
• Thinking pytest skips failed asserts
• Confusing syntax error with assertion failure

4. Identify the error in this unittest test case that will cause it to fail to run:

import unittest

class TestMath(unittest.TestCase):
    def test_add(self):
        assert 1 + 1 == 2

medium

A. Missing self.assertEqual method for assertion

B. Class name should not start with Test

C. Missing import for pytest

D. Function name should not start with test

Solution

1. Step 1: Check unittest assertion style

   unittest requires using self.assertEqual or other assert methods, not bare assert statements.

2. Step 2: Identify error cause

   Using bare assert inside unittest.TestCase method will not be recognized properly and may cause test to be ignored or fail.

3. Final Answer:

   Missing self.assertEqual method for assertion -> Option A

4. Quick Check:

   unittest needs self.assertEqual, not bare assert [OK]

Hint: Use self.assertEqual in unittest, not bare assert [OK]

Common Mistakes:

• Using bare assert in unittest tests
• Thinking pytest syntax works in unittest
• Ignoring class and method naming conventions

5. You have legacy tests written using nose that use classes and setup methods. You want to migrate to pytest but keep the setup logic. Which pytest feature helps you reuse setup code cleanly?

hard

A. pytest fixtures

B. unittest setUp method

C. nose plugins

D. pytest parametrize decorator

Solution

1. Step 1: Understand nose setup style

   nose uses setup methods in classes to prepare test environments.

2. Step 2: Identify pytest equivalent

   pytest uses fixtures to provide setup and teardown logic reusable across tests.

3. Step 3: Compare options

   unittest setUp is not used in pytest; nose plugins are legacy; parametrize is for test data variation.

4. Final Answer:

   pytest fixtures -> Option A

5. Quick Check:

   Setup reuse in pytest = fixtures [OK]

Hint: Use pytest fixtures for setup reuse [OK]

Common Mistakes:

• Trying to use unittest setUp in pytest
• Confusing parametrize with setup
• Relying on nose plugins in pytest