Python unittest how to#
Python unittest code#

# Now set the sys.argv to the unittest_args (leaving sys.argv alone)Īnd finally a sample test case (project_test.py) to test that the parameters are parsed correctly: import unittest Parser.add_argument('-level', type=int, default=0)

Now parser.py, which had to be in a separate file to avoid being in the _main_ module for the global reference to work: import sys Unittest.main(module=None, argv=sys.argv)

Python unittest code#

The code for that wrapper is basically the same as the code you already use for the single file case! You just need to put it into a separate file.ĮDIT: Added sample code below as requested.įirst, the new file to run the UTs (my_unittest.py): import sys You therefore have to remove the parameters before unittest is invoked.Ī simple way to do this is to create a wrapper module (say my_unittest.py) that looks for your extra parameters, strips them from sys.argv and then invokes the main entry in unittest. The problem you have is that the unittest argument parser simply does not understand this syntax. It can somehow support multiple test levels (either using the technique in the question, or using some other different mechanism).

It allows generating a single report for multiple-file unittests.This is not bad, but I'm looking for something cleaner.Ĭhanging the multiple-file test runner (i.e., python -m unittest discover foo '*test.py') to something else is fine, as long as: The pre-bounty (fine) solution suggests using system environment variables. How can I pass -level=3 to the individual unittests? If possible, I'd like to avoid dividing different-level tests to different files. usr/bin/python: No module named -level=3 $ python -m -level=3 unittest discover foo '*test.py' Python -m unittest discover: error: no such option: -level Everything I try fails, e.g.: $ python -m unittest discover -level=3 foo '*test.py'

Python unittest how to#

The problem is that I can't figure out how to pass the custom flag (in this case '-level=3' using discover. So now, I can run an individual unittest file, say foo/bar/_bar_test.py, with python foo/bar/_bar_test.py -level=3

The answer to this question explained very well how to get unittest and argparse to work well with each other. Since some of the tests are extremely slow, I've recently decided that tests should have 'levels'. Note that this uses unittest's discovery mode. Within foo's setup.py, I've added a custom 'test' command internally running python -m unittest discover foo '*test.py' Foo is a Python project with deep directory nesting, including ~30 unittest files in various subdirectories.