Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Optimal file structure organization of Python module unittests?

Tags:

Sadly I observed that there are are too many ways to keep your unittest in Python and they are not usually well documented.

I am looking for an "ultimate" structure, one would accomplish most of the below requirements:

  • be discoverable by test frameworks, including:
    • pytest
    • nosetests
    • tox
  • the tests should be outside the module files and in another directory than the module itself (maintenance), probably in a tests/ directory at package level.
  • it should be possible to just execute a test file (the test must be able to know where is the module that is supposed to test)

Please provide a sample test file that does a fake test, specify filename and directory.

like image 591
sorin Avatar asked Oct 07 '11 09:10

sorin


People also ask

How do you organize a Python project?

Organize your modules into packages. Each package must contain a special __init__.py file. Your project should generally consist of one top-level package, usually containing sub-packages. That top-level package usually shares the name of your project, and exists as a directory in the root of your project's repository.

Where should I put tests in python project?

Tests are put in files of the form test_*. py or *_test.py , and are usually placed in a directory called tests/ in a package's root.


1 Answers

Here's the approach I've been using:

Directory structure

# All __init__.py files are empty in this example.
app
    package_a
        __init__.py
        module_a.py
    package_b
        __init__.py
        module_b.py
    test
        __init__.py
        test_app.py
    __init__.py
main.py

main.py

# This is the application's front-end.
#
# The import will succeed if Python can find the `app` package, which
# will occur if the parent directory of app/ is in sys.path, either 
# because the user is running the script from within that parect directory
# or because the user has included the parent directory in the PYTHONPATH
# environment variable.

from app.package_a.module_a import aaa
print aaa(123, 456)

module_a.py

# We can import a sibling module like this.
from app.package_b.module_b import bbb
def aaa(s, t):
    return '{0} {1}'.format(s, bbb(t))

# We can also run module_a.py directly, using Python's -m option, which
# allows you to run a module like a script.
#
#    python -m app.package_a.module_a
if __name__ == '__main__':
    print aaa(111, 222)
    print bbb(333)

module_b.py

def bbb(s):
    return s + 1

test_app.py

import unittest

# From the point of view of testing code, our working modules
# are siblings. Imports work accordingly, as seen in module_a.
from app.package_a.module_a import aaa
from app.package_a.module_a import bbb

class TestApp(unittest.TestCase):

    def test_aaa(self):
        self.assertEqual(aaa(77, 88), '77 89')

    def test_bbb(self):
        self.assertEqual(bbb(99), 100)

# Simiarly, we can run our test modules directly as scripts using the -m option,
# or using nose.
#
#    python -m app.test.test_app
#    nosetests app/test/test_app.py

if __name__ == '__main__':
    unittest.main()
like image 147
FMc Avatar answered Oct 26 '22 11:10

FMc