PyTest vs unittest vs nose comparison - Test Execution Compared

Test Overview

This test checks a simple function using PyTest framework. It verifies that the function returns the expected result. This helps compare how PyTest runs tests versus unittest and nose.

Test Code - PyTest

PyTest

import pytest

def add(a, b):
    return a + b

def test_add():
    assert add(2, 3) == 5

Execution Trace - 5 Steps

Step	Action	System State	Assertion	Result
1	Test starts	PyTest test runner initializes	—	PASS
2	PyTest collects test functions starting with 'test_'	Test function 'test_add' found	—	PASS
3	PyTest runs test_add function	Function add(2, 3) is called	Check if add(2, 3) == 5	PASS
4	Assertion passes as 2 + 3 equals 5	Test completes successfully	assert add(2, 3) == 5	PASS
5	Test ends and report shows 1 test passed	Test summary displayed	—	PASS

Failure Scenario

Failing Condition: The add function returns wrong result, e.g., add(2, 3) returns 6

Execution Trace Quiz - 3 Questions

What does PyTest look for to find test functions?

A Functions ending with '_test'

B Functions starting with 'check_'

C Functions starting with 'test_'

D Functions with @test decorator

Key Result

PyTest is simple and flexible, allowing tests as plain functions with assert statements, unlike unittest which requires classes and methods. Nose is similar to PyTest but less maintained now.

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