PyTest vs unittest vs nose comparison - Quick Revision & Key Differences

Recall & Review

beginner

What is pytest and why is it popular?

pytest is a modern Python testing framework known for its simple syntax and powerful features. It is popular because it requires less boilerplate code, supports fixtures for setup, and has rich plugins.

beginner

What is unittest in Python?

unittest is Python's built-in testing framework. It uses a class-based approach and requires writing test cases as methods inside test classes.

intermediate

What was nose used for in Python testing?

nose was a testing framework that extended unittest to make testing easier. It is now mostly replaced by pytest and is no longer actively maintained.

intermediate

How does pytest handle test discovery compared to unittest?

pytest automatically finds tests by looking for files and functions starting with test_. unittest requires tests to be inside classes derived from unittest.TestCase.

beginner

Why might someone choose pytest over unittest or nose?

Because pytest offers simpler syntax, better fixtures, more plugins, and active community support, making tests easier to write and maintain.

Which testing framework is built into Python by default?

A pytest

B nose

C tox

D unittest

unittest is included in Python's standard library, so no extra installation is needed.

Which framework is known for requiring less boilerplate code and supports fixtures?

A pytest

B doctest

C nose

D unittest

pytest uses simple function-based tests and fixtures to reduce boilerplate.

Which framework is no longer actively maintained and mostly replaced by pytest?

A nose

B unittest

C pytest

D robotframework

nose is deprecated and replaced by pytest for most use cases.

How does unittest require tests to be organized?

A As standalone functions

B Inside classes derived from unittest.TestCase

C In YAML files

D In JSON format

unittest uses class-based test cases inheriting from unittest.TestCase.

Which framework automatically discovers tests by looking for files and functions starting with 'test_'?

A unittest

B nose

C pytest

D behave

pytest uses simple naming conventions to find tests automatically.

Explain the main differences between pytest, unittest, and nose.

Think about syntax, maintenance, and features.

Why is pytest generally preferred over unittest and nose for new Python projects?

Focus on ease of use and community support.

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