p!ranha?

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <title>25.3. unittest — Unit testing framework — Python 2.7.5 documentation</title> <link rel="stylesheet" href="../_static/default.css" type="text/css" /> <link rel="stylesheet" href="../_static/pygments.css" type="text/css" /> <script type="text/javascript"> var DOCUMENTATION_OPTIONS = { URL_ROOT: '../', VERSION: '2.7.5', COLLAPSE_INDEX: false, FILE_SUFFIX: '.html', HAS_SOURCE: true }; </script> <script type="text/javascript" src="../_static/jquery.js"></script> <script type="text/javascript" src="../_static/underscore.js"></script> <script type="text/javascript" src="../_static/doctools.js"></script> <script type="text/javascript" src="../_static/sidebar.js"></script> <link rel="search" type="application/opensearchdescription+xml" title="Search within Python 2.7.5 documentation" href="../_static/opensearch.xml"/> <link rel="author" title="About these documents" href="../about.html" /> <link rel="copyright" title="Copyright" href="../copyright.html" /> <link rel="top" title="Python 2.7.5 documentation" href="../index.html" /> <link rel="up" title="25. Development Tools" href="development.html" /> <link rel="next" title="25.4. 2to3 - Automated Python 2 to 3 code translation" href="2to3.html" /> <link rel="prev" title="25.2. doctest — Test interactive Python examples" href="doctest.html" /> <link rel="shortcut icon" type="image/png" href="../_static/py.png" /> <script type="text/javascript" src="../_static/copybutton.js"></script> </head> <body> <div class="related"> <h3>Navigation</h3> <ul> <li class="right" style="margin-right: 10px"> <a href="../genindex.html" title="General Index" accesskey="I">index</a></li> <li class="right" > <a href="../py-modindex.html" title="Python Module Index" >modules</a> |</li> <li class="right" > <a href="2to3.html" title="25.4. 2to3 - Automated Python 2 to 3 code translation" accesskey="N">next</a> |</li> <li class="right" > <a href="doctest.html" title="25.2. doctest — Test interactive Python examples" accesskey="P">previous</a> |</li> <li><img src="../_static/py.png" alt="" style="vertical-align: middle; margin-top: -1px"/></li> <li><a href="http://www.python.org/">Python</a> »</li> <li> <a href="../index.html">Python 2.7.5 documentation</a> » </li> <li><a href="index.html" >The Python Standard Library</a> »</li> <li><a href="development.html" accesskey="U">25. Development Tools</a> »</li> </ul> </div> <div class="document"> <div class="documentwrapper"> <div class="bodywrapper"> <div class="body"> <div class="section" id="module-unittest"> <h1>25.3. <a class="reference internal" href="#module-unittest" title="unittest: Unit testing framework for Python."><tt class="xref py py-mod docutils literal">unittest</tt></a> — Unit testing framework<a class="headerlink" href="#module-unittest" title="Permalink to this headline">¶</a></h1> New in version 2.1. (If you are already familiar with the basic concepts of testing, you might want to skip to <a class="reference internal" href="#assert-methods">the list of assert methods</a>.) The Python unit testing framework, sometimes referred to as “PyUnit,” is a Python language version of JUnit, by Kent Beck and Erich Gamma. JUnit is, in turn, a Java version of Kent’s Smalltalk testing framework. Each is the de facto standard unit testing framework for its respective language. <a class="reference internal" href="#module-unittest" title="unittest: Unit testing framework for Python."><tt class="xref py py-mod docutils literal">unittest</tt></a> supports test automation, sharing of setup and shutdown code for tests, aggregation of tests into collections, and independence of the tests from the reporting framework. The <a class="reference internal" href="#module-unittest" title="unittest: Unit testing framework for Python."><tt class="xref py py-mod docutils literal">unittest</tt></a> module provides classes that make it easy to support these qualities for a set of tests. To achieve this, <a class="reference internal" href="#module-unittest" title="unittest: Unit testing framework for Python."><tt class="xref py py-mod docutils literal">unittest</tt></a> supports some important concepts: <dl class="docutils"> <dt>test fixture</dt> <dd>A test fixture represents the preparation needed to perform one or more tests, and any associate cleanup actions. This may involve, for example, creating temporary or proxy databases, directories, or starting a server process.</dd> <dt>test case</dt> <dd>A test case is the smallest unit of testing. It checks for a specific response to a particular set of inputs. <a class="reference internal" href="#module-unittest" title="unittest: Unit testing framework for Python."><tt class="xref py py-mod docutils literal">unittest</tt></a> provides a base class, <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a>, which may be used to create new test cases.</dd> <dt>test suite</dt> <dd>A test suite is a collection of test cases, test suites, or both. It is used to aggregate tests that should be executed together.</dd> <dt>test runner</dt> <dd>A test runner is a component which orchestrates the execution of tests and provides the outcome to the user. The runner may use a graphical interface, a textual interface, or return a special value to indicate the results of executing the tests.</dd> </dl> The test case and test fixture concepts are supported through the <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> and <a class="reference internal" href="#unittest.FunctionTestCase" title="unittest.FunctionTestCase"><tt class="xref py py-class docutils literal">FunctionTestCase</tt></a> classes; the former should be used when creating new tests, and the latter can be used when integrating existing test code with a <a class="reference internal" href="#module-unittest" title="unittest: Unit testing framework for Python."><tt class="xref py py-mod docutils literal">unittest</tt></a>-driven framework. When building test fixtures using <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a>, the <a class="reference internal" href="#unittest.TestCase.setUp" title="unittest.TestCase.setUp"><tt class="xref py py-meth docutils literal">setUp()</tt></a> and <a class="reference internal" href="#unittest.TestCase.tearDown" title="unittest.TestCase.tearDown"><tt class="xref py py-meth docutils literal">tearDown()</tt></a> methods can be overridden to provide initialization and cleanup for the fixture. With <a class="reference internal" href="#unittest.FunctionTestCase" title="unittest.FunctionTestCase"><tt class="xref py py-class docutils literal">FunctionTestCase</tt></a>, existing functions can be passed to the constructor for these purposes. When the test is run, the fixture initialization is run first; if it succeeds, the cleanup method is run after the test has been executed, regardless of the outcome of the test. Each instance of the <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> will only be used to run a single test method, so a new fixture is created for each test. Test suites are implemented by the <a class="reference internal" href="#unittest.TestSuite" title="unittest.TestSuite"><tt class="xref py py-class docutils literal">TestSuite</tt></a> class. This class allows individual tests and test suites to be aggregated; when the suite is executed, all tests added directly to the suite and in “child” test suites are run. A test runner is an object that provides a single method, <tt class="xref py py-meth docutils literal">run()</tt>, which accepts a <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> or <a class="reference internal" href="#unittest.TestSuite" title="unittest.TestSuite"><tt class="xref py py-class docutils literal">TestSuite</tt></a> object as a parameter, and returns a result object. The class <a class="reference internal" href="#unittest.TestResult" title="unittest.TestResult"><tt class="xref py py-class docutils literal">TestResult</tt></a> is provided for use as the result object. <a class="reference internal" href="#module-unittest" title="unittest: Unit testing framework for Python."><tt class="xref py py-mod docutils literal">unittest</tt></a> provides the <a class="reference internal" href="#unittest.TextTestRunner" title="unittest.TextTestRunner"><tt class="xref py py-class docutils literal">TextTestRunner</tt></a> as an example test runner which reports test results on the standard error stream by default. Alternate runners can be implemented for other environments (such as graphical environments) without any need to derive from a specific class. <div class="admonition-see-also admonition seealso"> See also <dl class="last docutils"> <dt>Module <a class="reference internal" href="doctest.html#module-doctest" title="doctest: Test pieces of code within docstrings."><tt class="xref py py-mod docutils literal">doctest</tt></a></dt> <dd>Another test-support module with a very different flavor.</dd> <dt><a class="reference external" href="http://pypi.python.org/pypi/unittest2">unittest2: A backport of new unittest features for Python 2.4-2.6</a></dt> <dd>Many new features were added to unittest in Python 2.7, including test discovery. unittest2 allows you to use these features with earlier versions of Python.</dd> <dt><a class="reference external" href="http://www.XProgramming.com/testfram.htm">Simple Smalltalk Testing: With Patterns</a></dt> <dd>Kent Beck’s original paper on testing frameworks using the pattern shared by <a class="reference internal" href="#module-unittest" title="unittest: Unit testing framework for Python."><tt class="xref py py-mod docutils literal">unittest</tt></a>.</dd> <dt><a class="reference external" href="http://code.google.com/p/python-nose/">Nose</a> and <a class="reference external" href="http://pytest.org">py.test</a></dt> <dd>Third-party unittest frameworks with a lighter-weight syntax for writing tests. For example, <tt class="docutils literal">assert func(10) == 42</tt>.</dd> <dt><a class="reference external" href="http://pycheesecake.org/wiki/PythonTestingToolsTaxonomy">The Python Testing Tools Taxonomy</a></dt> <dd>An extensive list of Python testing tools including functional testing frameworks and mock object libraries.</dd> <dt><a class="reference external" href="http://lists.idyll.org/listinfo/testing-in-python">Testing in Python Mailing List</a></dt> <dd>A special-interest-group for discussion of testing, and testing tools, in Python.</dd> </dl> </div> <div class="section" id="basic-example"> <h2>25.3.1. Basic example<a class="headerlink" href="#basic-example" title="Permalink to this headline">¶</a></h2> The <a class="reference internal" href="#module-unittest" title="unittest: Unit testing framework for Python."><tt class="xref py py-mod docutils literal">unittest</tt></a> module provides a rich set of tools for constructing and running tests. This section demonstrates that a small subset of the tools suffice to meet the needs of most users. Here is a short script to test three functions from the <a class="reference internal" href="random.html#module-random" title="random: Generate pseudo-random numbers with various common distributions."><tt class="xref py py-mod docutils literal">random</tt></a> module: <div class="highlight-python"><div class="highlight"><pre>import random import unittest class TestSequenceFunctions(unittest.TestCase): def setUp(self): self.seq = range(10) def test_shuffle(self): # make sure the shuffled sequence does not lose any elements random.shuffle(self.seq) self.seq.sort() self.assertEqual(self.seq, range(10)) # should raise an exception for an immutable sequence self.assertRaises(TypeError, random.shuffle, (1,2,3)) def test_choice(self): element = random.choice(self.seq) self.assertTrue(element in self.seq) def test_sample(self): with self.assertRaises(ValueError): random.sample(self.seq, 20) for element in random.sample(self.seq, 5): self.assertTrue(element in self.seq) if __name__ == '__main__': unittest.main() </pre></div> </div> A testcase is created by subclassing <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">unittest.TestCase</tt></a>. The three individual tests are defined with methods whose names start with the letters <tt class="docutils literal">test</tt>. This naming convention informs the test runner about which methods represent tests. The crux of each test is a call to <a class="reference internal" href="#unittest.TestCase.assertEqual" title="unittest.TestCase.assertEqual"><tt class="xref py py-meth docutils literal">assertEqual()</tt></a> to check for an expected result; <a class="reference internal" href="#unittest.TestCase.assertTrue" title="unittest.TestCase.assertTrue"><tt class="xref py py-meth docutils literal">assertTrue()</tt></a> to verify a condition; or <a class="reference internal" href="#unittest.TestCase.assertRaises" title="unittest.TestCase.assertRaises"><tt class="xref py py-meth docutils literal">assertRaises()</tt></a> to verify that an expected exception gets raised. These methods are used instead of the <a class="reference internal" href="../reference/simple_stmts.html#assert"><tt class="xref std std-keyword docutils literal">assert</tt></a> statement so the test runner can accumulate all test results and produce a report. When a <a class="reference internal" href="#unittest.TestCase.setUp" title="unittest.TestCase.setUp"><tt class="xref py py-meth docutils literal">setUp()</tt></a> method is defined, the test runner will run that method prior to each test. Likewise, if a <a class="reference internal" href="#unittest.TestCase.tearDown" title="unittest.TestCase.tearDown"><tt class="xref py py-meth docutils literal">tearDown()</tt></a> method is defined, the test runner will invoke that method after each test. In the example, <a class="reference internal" href="#unittest.TestCase.setUp" title="unittest.TestCase.setUp"><tt class="xref py py-meth docutils literal">setUp()</tt></a> was used to create a fresh sequence for each test. The final block shows a simple way to run the tests. <a class="reference internal" href="#unittest.main" title="unittest.main"><tt class="xref py py-func docutils literal">unittest.main()</tt></a> provides a command-line interface to the test script. When run from the command line, the above script produces an output that looks like this: <div class="highlight-python"><pre>... ---------------------------------------------------------------------- Ran 3 tests in 0.000s OK</pre> </div> Instead of <a class="reference internal" href="#unittest.main" title="unittest.main"><tt class="xref py py-func docutils literal">unittest.main()</tt></a>, there are other ways to run the tests with a finer level of control, less terse output, and no requirement to be run from the command line. For example, the last two lines may be replaced with: <div class="highlight-python"><div class="highlight"><pre>suite = unittest.TestLoader().loadTestsFromTestCase(TestSequenceFunctions) unittest.TextTestRunner(verbosity=2).run(suite) </pre></div> </div> Running the revised script from the interpreter or another script produces the following output: <div class="highlight-python"><pre>test_choice (__main__.TestSequenceFunctions) ... ok test_sample (__main__.TestSequenceFunctions) ... ok test_shuffle (__main__.TestSequenceFunctions) ... ok ---------------------------------------------------------------------- Ran 3 tests in 0.110s OK</pre> </div> The above examples show the most commonly used <a class="reference internal" href="#module-unittest" title="unittest: Unit testing framework for Python."><tt class="xref py py-mod docutils literal">unittest</tt></a> features which are sufficient to meet many everyday testing needs. The remainder of the documentation explores the full feature set from first principles. </div> <div class="section" id="command-line-interface"> <h2>25.3.2. Command-Line Interface<a class="headerlink" href="#command-line-interface" title="Permalink to this headline">¶</a></h2> The unittest module can be used from the command line to run tests from modules, classes or even individual test methods: <div class="highlight-python"><pre>python -m unittest test_module1 test_module2 python -m unittest test_module.TestClass python -m unittest test_module.TestClass.test_method</pre> </div> You can pass in a list with any combination of module names, and fully qualified class or method names. You can run tests with more detail (higher verbosity) by passing in the -v flag: <div class="highlight-python"><pre>python -m unittest -v test_module</pre> </div> For a list of all the command-line options: <div class="highlight-python"><pre>python -m unittest -h</pre> </div> Changed in version 2.7: In earlier versions it was only possible to run individual test methods and not modules or classes. <div class="section" id="command-line-options"> <h3>25.3.2.1. Command-line options<a class="headerlink" href="#command-line-options" title="Permalink to this headline">¶</a></h3> unittest supports these command-line options: <dl class="cmdoption"> <dt id="cmdoption-unittest-b"> <tt class="descname">-b</tt><tt class="descclassname"></tt><tt class="descclassname">, </tt><tt class="descname">--buffer</tt><tt class="descclassname"></tt><a class="headerlink" href="#cmdoption-unittest-b" title="Permalink to this definition">¶</a></dt> <dd>The standard output and standard error streams are buffered during the test run. Output during a passing test is discarded. Output is echoed normally on test fail or error and is added to the failure messages. </dd></dl> <dl class="cmdoption"> <dt id="cmdoption-unittest-c"> <tt class="descname">-c</tt><tt class="descclassname"></tt><tt class="descclassname">, </tt><tt class="descname">--catch</tt><tt class="descclassname"></tt><a class="headerlink" href="#cmdoption-unittest-c" title="Permalink to this definition">¶</a></dt> <dd>Control-C during the test run waits for the current test to end and then reports all the results so far. A second control-C raises the normal <a class="reference internal" href="exceptions.html#exceptions.KeyboardInterrupt" title="exceptions.KeyboardInterrupt"><tt class="xref py py-exc docutils literal">KeyboardInterrupt</tt></a> exception. See <a class="reference internal" href="#signal-handling">Signal Handling</a> for the functions that provide this functionality. </dd></dl> <dl class="cmdoption"> <dt id="cmdoption-unittest-f"> <tt class="descname">-f</tt><tt class="descclassname"></tt><tt class="descclassname">, </tt><tt class="descname">--failfast</tt><tt class="descclassname"></tt><a class="headerlink" href="#cmdoption-unittest-f" title="Permalink to this definition">¶</a></dt> <dd>Stop the test run on the first error or failure. </dd></dl> New in version 2.7: The command-line options <tt class="docutils literal">-b</tt>, <tt class="docutils literal">-c</tt> and <tt class="docutils literal">-f</tt> were added. The command line can also be used for test discovery, for running all of the tests in a project or just a subset. </div> </div> <div class="section" id="test-discovery"> <h2>25.3.3. Test Discovery<a class="headerlink" href="#test-discovery" title="Permalink to this headline">¶</a></h2> New in version 2.7. Unittest supports simple test discovery. In order to be compatible with test discovery, all of the test files must be <a class="reference internal" href="../tutorial/modules.html#tut-modules">modules</a> or <a class="reference internal" href="../tutorial/modules.html#tut-packages">packages</a> importable from the top-level directory of the project (this means that their filenames must be valid <a class="reference internal" href="../reference/lexical_analysis.html#identifiers">identifiers</a>). Test discovery is implemented in <a class="reference internal" href="#unittest.TestLoader.discover" title="unittest.TestLoader.discover"><tt class="xref py py-meth docutils literal">TestLoader.discover()</tt></a>, but can also be used from the command line. The basic command-line usage is: <div class="highlight-python"><pre>cd project_directory python -m unittest discover</pre> </div> The <tt class="docutils literal">discover</tt> sub-command has the following options: <dl class="cmdoption"> <dt id="cmdoption-unittest-discover-v"> <tt class="descname">-v</tt><tt class="descclassname"></tt><tt class="descclassname">, </tt><tt class="descname">--verbose</tt><tt class="descclassname"></tt><a class="headerlink" href="#cmdoption-unittest-discover-v" title="Permalink to this definition">¶</a></dt> <dd>Verbose output </dd></dl> <dl class="cmdoption"> <dt id="cmdoption-unittest-discover-s"> <tt class="descname">-s</tt><tt class="descclassname"></tt><tt class="descclassname">, </tt><tt class="descname">--start-directory</tt><tt class="descclassname"> directory</tt><a class="headerlink" href="#cmdoption-unittest-discover-s" title="Permalink to this definition">¶</a></dt> <dd>Directory to start discovery (<tt class="docutils literal">.</tt> default) </dd></dl> <dl class="cmdoption"> <dt id="cmdoption-unittest-discover-p"> <tt class="descname">-p</tt><tt class="descclassname"></tt><tt class="descclassname">, </tt><tt class="descname">--pattern</tt><tt class="descclassname"> pattern</tt><a class="headerlink" href="#cmdoption-unittest-discover-p" title="Permalink to this definition">¶</a></dt> <dd>Pattern to match test files (<tt class="docutils literal">test*.py</tt> default) </dd></dl> <dl class="cmdoption"> <dt id="cmdoption-unittest-discover-t"> <tt class="descname">-t</tt><tt class="descclassname"></tt><tt class="descclassname">, </tt><tt class="descname">--top-level-directory</tt><tt class="descclassname"> directory</tt><a class="headerlink" href="#cmdoption-unittest-discover-t" title="Permalink to this definition">¶</a></dt> <dd>Top level directory of project (defaults to start directory) </dd></dl> The <a class="reference internal" href="#cmdoption-unittest-discover-s">-s</a>, <a class="reference internal" href="#cmdoption-unittest-discover-p">-p</a>, and <a class="reference internal" href="#cmdoption-unittest-discover-t">-t</a> options can be passed in as positional arguments in that order. The following two command lines are equivalent: <div class="highlight-python"><pre>python -m unittest discover -s project_directory -p '*_test.py' python -m unittest discover project_directory '*_test.py'</pre> </div> As well as being a path it is possible to pass a package name, for example <tt class="docutils literal">myproject.subpackage.test</tt>, as the start directory. The package name you supply will then be imported and its location on the filesystem will be used as the start directory. <div class="admonition caution"> Caution Test discovery loads tests by importing them. Once test discovery has found all the test files from the start directory you specify it turns the paths into package names to import. For example <tt class="file docutils literal">foo/bar/baz.py</tt> will be imported as <tt class="docutils literal">foo.bar.baz</tt>. If you have a package installed globally and attempt test discovery on a different copy of the package then the import could happen from the wrong place. If this happens test discovery will warn you and exit. If you supply the start directory as a package name rather than a path to a directory then discover assumes that whichever location it imports from is the location you intended, so you will not get the warning. </div> Test modules and packages can customize test loading and discovery by through the <a class="reference internal" href="#load-tests-protocol">load_tests protocol</a>. </div> <div class="section" id="organizing-test-code"> <h2>25.3.4. Organizing test code<a class="headerlink" href="#organizing-test-code" title="Permalink to this headline">¶</a></h2> The basic building blocks of unit testing are test cases — single scenarios that must be set up and checked for correctness. In <a class="reference internal" href="#module-unittest" title="unittest: Unit testing framework for Python."><tt class="xref py py-mod docutils literal">unittest</tt></a>, test cases are represented by instances of <a class="reference internal" href="#module-unittest" title="unittest: Unit testing framework for Python."><tt class="xref py py-mod docutils literal">unittest</tt></a>‘s <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> class. To make your own test cases you must write subclasses of <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a>, or use <a class="reference internal" href="#unittest.FunctionTestCase" title="unittest.FunctionTestCase"><tt class="xref py py-class docutils literal">FunctionTestCase</tt></a>. An instance of a <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a>-derived class is an object that can completely run a single test method, together with optional set-up and tidy-up code. The testing code of a <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> instance should be entirely self contained, such that it can be run either in isolation or in arbitrary combination with any number of other test cases. The simplest <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> subclass will simply override the <tt class="xref py py-meth docutils literal">runTest()</tt> method in order to perform specific testing code: <div class="highlight-python"><div class="highlight"><pre>import unittest class DefaultWidgetSizeTestCase(unittest.TestCase): def runTest(self): widget = Widget('The widget') self.assertEqual(widget.size(), (50, 50), 'incorrect default size') </pre></div> </div> Note that in order to test something, we use one of the <tt class="xref py py-meth docutils literal">assert*()</tt> methods provided by the <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> base class. If the test fails, an exception will be raised, and <a class="reference internal" href="#module-unittest" title="unittest: Unit testing framework for Python."><tt class="xref py py-mod docutils literal">unittest</tt></a> will identify the test case as a failure. Any other exceptions will be treated as errors. This helps you identify where the problem is: failures are caused by incorrect results - a 5 where you expected a 6. Errors are caused by incorrect code - e.g., a <a class="reference internal" href="exceptions.html#exceptions.TypeError" title="exceptions.TypeError"><tt class="xref py py-exc docutils literal">TypeError</tt></a> caused by an incorrect function call. The way to run a test case will be described later. For now, note that to construct an instance of such a test case, we call its constructor without arguments: <div class="highlight-python"><div class="highlight"><pre>testCase = DefaultWidgetSizeTestCase() </pre></div> </div> Now, such test cases can be numerous, and their set-up can be repetitive. In the above case, constructing a <tt class="xref py py-class docutils literal">Widget</tt> in each of 100 Widget test case subclasses would mean unsightly duplication. Luckily, we can factor out such set-up code by implementing a method called <a class="reference internal" href="#unittest.TestCase.setUp" title="unittest.TestCase.setUp"><tt class="xref py py-meth docutils literal">setUp()</tt></a>, which the testing framework will automatically call for us when we run the test: <div class="highlight-python"><div class="highlight"><pre>import unittest class SimpleWidgetTestCase(unittest.TestCase): def setUp(self): self.widget = Widget('The widget') class DefaultWidgetSizeTestCase(SimpleWidgetTestCase): def runTest(self): self.assertEqual(self.widget.size(), (50,50), 'incorrect default size') class WidgetResizeTestCase(SimpleWidgetTestCase): def runTest(self): self.widget.resize(100,150) self.assertEqual(self.widget.size(), (100,150), 'wrong size after resize') </pre></div> </div> If the <a class="reference internal" href="#unittest.TestCase.setUp" title="unittest.TestCase.setUp"><tt class="xref py py-meth docutils literal">setUp()</tt></a> method raises an exception while the test is running, the framework will consider the test to have suffered an error, and the <tt class="xref py py-meth docutils literal">runTest()</tt> method will not be executed. Similarly, we can provide a <a class="reference internal" href="#unittest.TestCase.tearDown" title="unittest.TestCase.tearDown"><tt class="xref py py-meth docutils literal">tearDown()</tt></a> method that tidies up after the <tt class="xref py py-meth docutils literal">runTest()</tt> method has been run: <div class="highlight-python"><div class="highlight"><pre>import unittest class SimpleWidgetTestCase(unittest.TestCase): def setUp(self): self.widget = Widget('The widget') def tearDown(self): self.widget.dispose() self.widget = None </pre></div> </div> If <a class="reference internal" href="#unittest.TestCase.setUp" title="unittest.TestCase.setUp"><tt class="xref py py-meth docutils literal">setUp()</tt></a> succeeded, the <a class="reference internal" href="#unittest.TestCase.tearDown" title="unittest.TestCase.tearDown"><tt class="xref py py-meth docutils literal">tearDown()</tt></a> method will be run whether <tt class="xref py py-meth docutils literal">runTest()</tt> succeeded or not. Such a working environment for the testing code is called a fixture. Often, many small test cases will use the same fixture. In this case, we would end up subclassing <tt class="xref py py-class docutils literal">SimpleWidgetTestCase</tt> into many small one-method classes such as <tt class="xref py py-class docutils literal">DefaultWidgetSizeTestCase</tt>. This is time-consuming and discouraging, so in the same vein as JUnit, <a class="reference internal" href="#module-unittest" title="unittest: Unit testing framework for Python."><tt class="xref py py-mod docutils literal">unittest</tt></a> provides a simpler mechanism: <div class="highlight-python"><div class="highlight"><pre>import unittest class WidgetTestCase(unittest.TestCase): def setUp(self): self.widget = Widget('The widget') def tearDown(self): self.widget.dispose() self.widget = None def test_default_size(self): self.assertEqual(self.widget.size(), (50,50), 'incorrect default size') def test_resize(self): self.widget.resize(100,150) self.assertEqual(self.widget.size(), (100,150), 'wrong size after resize') </pre></div> </div> Here we have not provided a <tt class="xref py py-meth docutils literal">runTest()</tt> method, but have instead provided two different test methods. Class instances will now each run one of the <tt class="xref py py-meth docutils literal">test_*()</tt> methods, with <tt class="docutils literal">self.widget</tt> created and destroyed separately for each instance. When creating an instance we must specify the test method it is to run. We do this by passing the method name in the constructor: <div class="highlight-python"><div class="highlight"><pre>defaultSizeTestCase = WidgetTestCase('test_default_size') resizeTestCase = WidgetTestCase('test_resize') </pre></div> </div> Test case instances are grouped together according to the features they test. <a class="reference internal" href="#module-unittest" title="unittest: Unit testing framework for Python."><tt class="xref py py-mod docutils literal">unittest</tt></a> provides a mechanism for this: the test suite, represented by <a class="reference internal" href="#module-unittest" title="unittest: Unit testing framework for Python."><tt class="xref py py-mod docutils literal">unittest</tt></a>‘s <a class="reference internal" href="#unittest.TestSuite" title="unittest.TestSuite"><tt class="xref py py-class docutils literal">TestSuite</tt></a> class: <div class="highlight-python"><div class="highlight"><pre>widgetTestSuite = unittest.TestSuite() widgetTestSuite.addTest(WidgetTestCase('test_default_size')) widgetTestSuite.addTest(WidgetTestCase('test_resize')) </pre></div> </div> For the ease of running tests, as we will see later, it is a good idea to provide in each test module a callable object that returns a pre-built test suite: <div class="highlight-python"><div class="highlight"><pre>def suite(): suite = unittest.TestSuite() suite.addTest(WidgetTestCase('test_default_size')) suite.addTest(WidgetTestCase('test_resize')) return suite </pre></div> </div> or even: <div class="highlight-python"><div class="highlight"><pre>def suite(): tests = ['test_default_size', 'test_resize'] return unittest.TestSuite(map(WidgetTestCase, tests)) </pre></div> </div> Since it is a common pattern to create a <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> subclass with many similarly named test functions, <a class="reference internal" href="#module-unittest" title="unittest: Unit testing framework for Python."><tt class="xref py py-mod docutils literal">unittest</tt></a> provides a <a class="reference internal" href="#unittest.TestLoader" title="unittest.TestLoader"><tt class="xref py py-class docutils literal">TestLoader</tt></a> class that can be used to automate the process of creating a test suite and populating it with individual tests. For example, <div class="highlight-python"><div class="highlight"><pre>suite = unittest.TestLoader().loadTestsFromTestCase(WidgetTestCase) </pre></div> </div> will create a test suite that will run <tt class="docutils literal">WidgetTestCase.test_default_size()</tt> and <tt class="docutils literal">WidgetTestCase.test_resize</tt>. <a class="reference internal" href="#unittest.TestLoader" title="unittest.TestLoader"><tt class="xref py py-class docutils literal">TestLoader</tt></a> uses the <tt class="docutils literal">'test'</tt> method name prefix to identify test methods automatically. Note that the order in which the various test cases will be run is determined by sorting the test function names with respect to the built-in ordering for strings. Often it is desirable to group suites of test cases together, so as to run tests for the whole system at once. This is easy, since <a class="reference internal" href="#unittest.TestSuite" title="unittest.TestSuite"><tt class="xref py py-class docutils literal">TestSuite</tt></a> instances can be added to a <a class="reference internal" href="#unittest.TestSuite" title="unittest.TestSuite"><tt class="xref py py-class docutils literal">TestSuite</tt></a> just as <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> instances can be added to a <a class="reference internal" href="#unittest.TestSuite" title="unittest.TestSuite"><tt class="xref py py-class docutils literal">TestSuite</tt></a>: <div class="highlight-python"><div class="highlight"><pre>suite1 = module1.TheTestSuite() suite2 = module2.TheTestSuite() alltests = unittest.TestSuite([suite1, suite2]) </pre></div> </div> You can place the definitions of test cases and test suites in the same modules as the code they are to test (such as <tt class="file docutils literal">widget.py</tt>), but there are several advantages to placing the test code in a separate module, such as <tt class="file docutils literal">test_widget.py</tt>: <ul class="simple"> <li>The test module can be run standalone from the command line.</li> <li>The test code can more easily be separated from shipped code.</li> <li>There is less temptation to change test code to fit the code it tests without a good reason.</li> <li>Test code should be modified much less frequently than the code it tests.</li> <li>Tested code can be refactored more easily.</li> <li>Tests for modules written in C must be in separate modules anyway, so why not be consistent?</li> <li>If the testing strategy changes, there is no need to change the source code.</li> </ul> </div> <div class="section" id="re-using-old-test-code"> <h2>25.3.5. Re-using old test code<a class="headerlink" href="#re-using-old-test-code" title="Permalink to this headline">¶</a></h2> Some users will find that they have existing test code that they would like to run from <a class="reference internal" href="#module-unittest" title="unittest: Unit testing framework for Python."><tt class="xref py py-mod docutils literal">unittest</tt></a>, without converting every old test function to a <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> subclass. For this reason, <a class="reference internal" href="#module-unittest" title="unittest: Unit testing framework for Python."><tt class="xref py py-mod docutils literal">unittest</tt></a> provides a <a class="reference internal" href="#unittest.FunctionTestCase" title="unittest.FunctionTestCase"><tt class="xref py py-class docutils literal">FunctionTestCase</tt></a> class. This subclass of <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> can be used to wrap an existing test function. Set-up and tear-down functions can also be provided. Given the following test function: <div class="highlight-python"><div class="highlight"><pre>def testSomething(): something = makeSomething() assert something.name is not None # ... </pre></div> </div> one can create an equivalent test case instance as follows: <div class="highlight-python"><div class="highlight"><pre>testcase = unittest.FunctionTestCase(testSomething) </pre></div> </div> If there are additional set-up and tear-down methods that should be called as part of the test case’s operation, they can also be provided like so: <div class="highlight-python"><div class="highlight"><pre>testcase = unittest.FunctionTestCase(testSomething, setUp=makeSomethingDB, tearDown=deleteSomethingDB) </pre></div> </div> To make migrating existing test suites easier, <a class="reference internal" href="#module-unittest" title="unittest: Unit testing framework for Python."><tt class="xref py py-mod docutils literal">unittest</tt></a> supports tests raising <a class="reference internal" href="exceptions.html#exceptions.AssertionError" title="exceptions.AssertionError"><tt class="xref py py-exc docutils literal">AssertionError</tt></a> to indicate test failure. However, it is recommended that you use the explicit <tt class="xref py py-meth docutils literal">TestCase.fail*()</tt> and <tt class="xref py py-meth docutils literal">TestCase.assert*()</tt> methods instead, as future versions of <a class="reference internal" href="#module-unittest" title="unittest: Unit testing framework for Python."><tt class="xref py py-mod docutils literal">unittest</tt></a> may treat <a class="reference internal" href="exceptions.html#exceptions.AssertionError" title="exceptions.AssertionError"><tt class="xref py py-exc docutils literal">AssertionError</tt></a> differently. <div class="admonition note"> Note Even though <a class="reference internal" href="#unittest.FunctionTestCase" title="unittest.FunctionTestCase"><tt class="xref py py-class docutils literal">FunctionTestCase</tt></a> can be used to quickly convert an existing test base over to a <a class="reference internal" href="#module-unittest" title="unittest: Unit testing framework for Python."><tt class="xref py py-mod docutils literal">unittest</tt></a>-based system, this approach is not recommended. Taking the time to set up proper <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> subclasses will make future test refactorings infinitely easier. </div> In some cases, the existing tests may have been written using the <a class="reference internal" href="doctest.html#module-doctest" title="doctest: Test pieces of code within docstrings."><tt class="xref py py-mod docutils literal">doctest</tt></a> module. If so, <a class="reference internal" href="doctest.html#module-doctest" title="doctest: Test pieces of code within docstrings."><tt class="xref py py-mod docutils literal">doctest</tt></a> provides a <tt class="xref py py-class docutils literal">DocTestSuite</tt> class that can automatically build <a class="reference internal" href="#unittest.TestSuite" title="unittest.TestSuite"><tt class="xref py py-class docutils literal">unittest.TestSuite</tt></a> instances from the existing <a class="reference internal" href="doctest.html#module-doctest" title="doctest: Test pieces of code within docstrings."><tt class="xref py py-mod docutils literal">doctest</tt></a>-based tests. </div> <div class="section" id="skipping-tests-and-expected-failures"> <h2>25.3.6. Skipping tests and expected failures<a class="headerlink" href="#skipping-tests-and-expected-failures" title="Permalink to this headline">¶</a></h2> New in version 2.7. Unittest supports skipping individual test methods and even whole classes of tests. In addition, it supports marking a test as a “expected failure,” a test that is broken and will fail, but shouldn’t be counted as a failure on a <a class="reference internal" href="#unittest.TestResult" title="unittest.TestResult"><tt class="xref py py-class docutils literal">TestResult</tt></a>. Skipping a test is simply a matter of using the <a class="reference internal" href="#unittest.skip" title="unittest.skip"><tt class="xref py py-func docutils literal">skip()</tt></a> <a class="reference internal" href="../glossary.html#term-decorator">decorator</a> or one of its conditional variants. Basic skipping looks like this: <div class="highlight-python"><div class="highlight"><pre>class MyTestCase(unittest.TestCase): @unittest.skip("demonstrating skipping") def test_nothing(self): self.fail("shouldn't happen") @unittest.skipIf(mylib.__version__ < (1, 3), "not supported in this library version") def test_format(self): # Tests that work for only a certain version of the library. pass @unittest.skipUnless(sys.platform.startswith("win"), "requires Windows") def test_windows_support(self): # windows specific testing code pass </pre></div> </div> This is the output of running the example above in verbose mode: <div class="highlight-python"><pre>test_format (__main__.MyTestCase) ... skipped 'not supported in this library version' test_nothing (__main__.MyTestCase) ... skipped 'demonstrating skipping' test_windows_support (__main__.MyTestCase) ... skipped 'requires Windows' ---------------------------------------------------------------------- Ran 3 tests in 0.005s OK (skipped=3)</pre> </div> Classes can be skipped just like methods: <div class="highlight-python"><div class="highlight"><pre>@unittest.skip("showing class skipping") class MySkippedTestCase(unittest.TestCase): def test_not_run(self): pass </pre></div> </div> <a class="reference internal" href="#unittest.TestCase.setUp" title="unittest.TestCase.setUp"><tt class="xref py py-meth docutils literal">TestCase.setUp()</tt></a> can also skip the test. This is useful when a resource that needs to be set up is not available. Expected failures use the <a class="reference internal" href="#unittest.expectedFailure" title="unittest.expectedFailure"><tt class="xref py py-func docutils literal">expectedFailure()</tt></a> decorator. <div class="highlight-python"><div class="highlight"><pre>class ExpectedFailureTestCase(unittest.TestCase): @unittest.expectedFailure def test_fail(self): self.assertEqual(1, 0, "broken") </pre></div> </div> It’s easy to roll your own skipping decorators by making a decorator that calls <a class="reference internal" href="#unittest.skip" title="unittest.skip"><tt class="xref py py-func docutils literal">skip()</tt></a> on the test when it wants it to be skipped. This decorator skips the test unless the passed object has a certain attribute: <div class="highlight-python"><div class="highlight"><pre>def skipUnlessHasattr(obj, attr): if hasattr(obj, attr): return lambda func: func return unittest.skip("{!r} doesn't have {!r}".format(obj, attr)) </pre></div> </div> The following decorators implement test skipping and expected failures: <dl class="function"> <dt id="unittest.skip"> <tt class="descclassname">unittest.</tt><tt class="descname">skip</tt><big>(</big>reason<big>)</big><a class="headerlink" href="#unittest.skip" title="Permalink to this definition">¶</a></dt> <dd>Unconditionally skip the decorated test. reason should describe why the test is being skipped. </dd></dl> <dl class="function"> <dt id="unittest.skipIf"> <tt class="descclassname">unittest.</tt><tt class="descname">skipIf</tt><big>(</big>condition, reason<big>)</big><a class="headerlink" href="#unittest.skipIf" title="Permalink to this definition">¶</a></dt> <dd>Skip the decorated test if condition is true. </dd></dl> <dl class="function"> <dt id="unittest.skipUnless"> <tt class="descclassname">unittest.</tt><tt class="descname">skipUnless</tt><big>(</big>condition, reason<big>)</big><a class="headerlink" href="#unittest.skipUnless" title="Permalink to this definition">¶</a></dt> <dd>Skip the decorated test unless condition is true. </dd></dl> <dl class="function"> <dt id="unittest.expectedFailure"> <tt class="descclassname">unittest.</tt><tt class="descname">expectedFailure</tt><big>(</big><big>)</big><a class="headerlink" href="#unittest.expectedFailure" title="Permalink to this definition">¶</a></dt> <dd>Mark the test as an expected failure. If the test fails when run, the test is not counted as a failure. </dd></dl> <dl class="exception"> <dt id="unittest.SkipTest"> exception <tt class="descclassname">unittest.</tt><tt class="descname">SkipTest</tt><big>(</big>reason<big>)</big><a class="headerlink" href="#unittest.SkipTest" title="Permalink to this definition">¶</a></dt> <dd>This exception is raised to skip a test. Usually you can use <a class="reference internal" href="#unittest.TestCase.skipTest" title="unittest.TestCase.skipTest"><tt class="xref py py-meth docutils literal">TestCase.skipTest()</tt></a> or one of the skipping decorators instead of raising this directly. </dd></dl> Skipped tests will not have <tt class="xref py py-meth docutils literal">setUp()</tt> or <tt class="xref py py-meth docutils literal">tearDown()</tt> run around them. Skipped classes will not have <tt class="xref py py-meth docutils literal">setUpClass()</tt> or <tt class="xref py py-meth docutils literal">tearDownClass()</tt> run. </div> <div class="section" id="classes-and-functions"> <h2>25.3.7. Classes and functions<a class="headerlink" href="#classes-and-functions" title="Permalink to this headline">¶</a></h2> This section describes in depth the API of <a class="reference internal" href="#module-unittest" title="unittest: Unit testing framework for Python."><tt class="xref py py-mod docutils literal">unittest</tt></a>. <div class="section" id="test-cases"> <h3>25.3.7.1. Test cases<a class="headerlink" href="#test-cases" title="Permalink to this headline">¶</a></h3> <dl class="class"> <dt id="unittest.TestCase"> class <tt class="descclassname">unittest.</tt><tt class="descname">TestCase</tt><big>(</big>methodName='runTest'<big>)</big><a class="headerlink" href="#unittest.TestCase" title="Permalink to this definition">¶</a></dt> <dd>Instances of the <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> class represent the smallest testable units in the <a class="reference internal" href="#module-unittest" title="unittest: Unit testing framework for Python."><tt class="xref py py-mod docutils literal">unittest</tt></a> universe. This class is intended to be used as a base class, with specific tests being implemented by concrete subclasses. This class implements the interface needed by the test runner to allow it to drive the test, and methods that the test code can use to check for and report various kinds of failure. Each instance of <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> will run a single test method: the method named methodName. If you remember, we had an earlier example that went something like this: <div class="highlight-python"><div class="highlight"><pre>def suite(): suite = unittest.TestSuite() suite.addTest(WidgetTestCase('test_default_size')) suite.addTest(WidgetTestCase('test_resize')) return suite </pre></div> </div> Here, we create two instances of <tt class="xref py py-class docutils literal">WidgetTestCase</tt>, each of which runs a single test. methodName defaults to <tt class="xref py py-meth docutils literal">runTest()</tt>. <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> instances provide three groups of methods: one group used to run the test, another used by the test implementation to check conditions and report failures, and some inquiry methods allowing information about the test itself to be gathered. Methods in the first group (running the test) are: <dl class="method"> <dt id="unittest.TestCase.setUp"> <tt class="descname">setUp</tt><big>(</big><big>)</big><a class="headerlink" href="#unittest.TestCase.setUp" title="Permalink to this definition">¶</a></dt> <dd>Method called to prepare the test fixture. This is called immediately before calling the test method; any exception raised by this method will be considered an error rather than a test failure. The default implementation does nothing. </dd></dl> <dl class="method"> <dt id="unittest.TestCase.tearDown"> <tt class="descname">tearDown</tt><big>(</big><big>)</big><a class="headerlink" href="#unittest.TestCase.tearDown" title="Permalink to this definition">¶</a></dt> <dd>Method called immediately after the test method has been called and the result recorded. This is called even if the test method raised an exception, so the implementation in subclasses may need to be particularly careful about checking internal state. Any exception raised by this method will be considered an error rather than a test failure. This method will only be called if the <a class="reference internal" href="#unittest.TestCase.setUp" title="unittest.TestCase.setUp"><tt class="xref py py-meth docutils literal">setUp()</tt></a> succeeds, regardless of the outcome of the test method. The default implementation does nothing. </dd></dl> <dl class="method"> <dt id="unittest.TestCase.setUpClass"> <tt class="descname">setUpClass</tt><big>(</big><big>)</big><a class="headerlink" href="#unittest.TestCase.setUpClass" title="Permalink to this definition">¶</a></dt> <dd>A class method called before tests in an individual class run. <tt class="docutils literal">setUpClass</tt> is called with the class as the only argument and must be decorated as a <a class="reference internal" href="functions.html#classmethod" title="classmethod"><tt class="xref py py-func docutils literal">classmethod()</tt></a>: <div class="highlight-python"><div class="highlight"><pre>@classmethod def setUpClass(cls): ... </pre></div> </div> See <a class="reference internal" href="#class-and-module-fixtures">Class and Module Fixtures</a> for more details. New in version 2.7. </dd></dl> <dl class="method"> <dt id="unittest.TestCase.tearDownClass"> <tt class="descname">tearDownClass</tt><big>(</big><big>)</big><a class="headerlink" href="#unittest.TestCase.tearDownClass" title="Permalink to this definition">¶</a></dt> <dd>A class method called after tests in an individual class have run. <tt class="docutils literal">tearDownClass</tt> is called with the class as the only argument and must be decorated as a <a class="reference internal" href="functions.html#classmethod" title="classmethod"><tt class="xref py py-meth docutils literal">classmethod()</tt></a>: <div class="highlight-python"><div class="highlight"><pre>@classmethod def tearDownClass(cls): ... </pre></div> </div> See <a class="reference internal" href="#class-and-module-fixtures">Class and Module Fixtures</a> for more details. New in version 2.7. </dd></dl> <dl class="method"> <dt id="unittest.TestCase.run"> <tt class="descname">run</tt><big>(</big>result=None<big>)</big><a class="headerlink" href="#unittest.TestCase.run" title="Permalink to this definition">¶</a></dt> <dd>Run the test, collecting the result into the test result object passed as result. If result is omitted or <tt class="docutils literal">None</tt>, a temporary result object is created (by calling the <a class="reference internal" href="#unittest.TestCase.defaultTestResult" title="unittest.TestCase.defaultTestResult"><tt class="xref py py-meth docutils literal">defaultTestResult()</tt></a> method) and used. The result object is not returned to <a class="reference internal" href="#unittest.TestCase.run" title="unittest.TestCase.run"><tt class="xref py py-meth docutils literal">run()</tt></a>‘s caller. The same effect may be had by simply calling the <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> instance. </dd></dl> <dl class="method"> <dt id="unittest.TestCase.skipTest"> <tt class="descname">skipTest</tt><big>(</big>reason<big>)</big><a class="headerlink" href="#unittest.TestCase.skipTest" title="Permalink to this definition">¶</a></dt> <dd>Calling this during a test method or <a class="reference internal" href="#unittest.TestCase.setUp" title="unittest.TestCase.setUp"><tt class="xref py py-meth docutils literal">setUp()</tt></a> skips the current test. See <a class="reference internal" href="#unittest-skipping">Skipping tests and expected failures</a> for more information. New in version 2.7. </dd></dl> <dl class="method"> <dt id="unittest.TestCase.debug"> <tt class="descname">debug</tt><big>(</big><big>)</big><a class="headerlink" href="#unittest.TestCase.debug" title="Permalink to this definition">¶</a></dt> <dd>Run the test without collecting the result. This allows exceptions raised by the test to be propagated to the caller, and can be used to support running tests under a debugger. </dd></dl> The <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> class provides a number of methods to check for and report failures, such as: <table border="1" class="docutils"> <colgroup> <col width="48%" /> <col width="34%" /> <col width="18%" /> </colgroup> <thead valign="bottom"> <tr class="row-odd"><th class="head">Method</th> <th class="head">Checks that</th> <th class="head">New in</th> </tr> </thead> <tbody valign="top"> <tr class="row-even"><td><a class="reference internal" href="#unittest.TestCase.assertEqual" title="unittest.TestCase.assertEqual"><tt class="xref py py-meth docutils literal">assertEqual(a, b)</tt></a></td> <td><tt class="docutils literal">a == b</tt></td> <td> </td> </tr> <tr class="row-odd"><td><a class="reference internal" href="#unittest.TestCase.assertNotEqual" title="unittest.TestCase.assertNotEqual"><tt class="xref py py-meth docutils literal">assertNotEqual(a, b)</tt></a></td> <td><tt class="docutils literal">a != b</tt></td> <td> </td> </tr> <tr class="row-even"><td><a class="reference internal" href="#unittest.TestCase.assertTrue" title="unittest.TestCase.assertTrue"><tt class="xref py py-meth docutils literal">assertTrue(x)</tt></a></td> <td><tt class="docutils literal">bool(x) is True</tt></td> <td> </td> </tr> <tr class="row-odd"><td><a class="reference internal" href="#unittest.TestCase.assertFalse" title="unittest.TestCase.assertFalse"><tt class="xref py py-meth docutils literal">assertFalse(x)</tt></a></td> <td><tt class="docutils literal">bool(x) is False</tt></td> <td> </td> </tr> <tr class="row-even"><td><a class="reference internal" href="#unittest.TestCase.assertIs" title="unittest.TestCase.assertIs"><tt class="xref py py-meth docutils literal">assertIs(a, b)</tt></a></td> <td><tt class="docutils literal">a is b</tt></td> <td>2.7</td> </tr> <tr class="row-odd"><td><a class="reference internal" href="#unittest.TestCase.assertIsNot" title="unittest.TestCase.assertIsNot"><tt class="xref py py-meth docutils literal">assertIsNot(a, b)</tt></a></td> <td><tt class="docutils literal">a is not b</tt></td> <td>2.7</td> </tr> <tr class="row-even"><td><a class="reference internal" href="#unittest.TestCase.assertIsNone" title="unittest.TestCase.assertIsNone"><tt class="xref py py-meth docutils literal">assertIsNone(x)</tt></a></td> <td><tt class="docutils literal">x is None</tt></td> <td>2.7</td> </tr> <tr class="row-odd"><td><a class="reference internal" href="#unittest.TestCase.assertIsNotNone" title="unittest.TestCase.assertIsNotNone"><tt class="xref py py-meth docutils literal">assertIsNotNone(x)</tt></a></td> <td><tt class="docutils literal">x is not None</tt></td> <td>2.7</td> </tr> <tr class="row-even"><td><a class="reference internal" href="#unittest.TestCase.assertIn" title="unittest.TestCase.assertIn"><tt class="xref py py-meth docutils literal">assertIn(a, b)</tt></a></td> <td><tt class="docutils literal">a in b</tt></td> <td>2.7</td> </tr> <tr class="row-odd"><td><a class="reference internal" href="#unittest.TestCase.assertNotIn" title="unittest.TestCase.assertNotIn"><tt class="xref py py-meth docutils literal">assertNotIn(a, b)</tt></a></td> <td><tt class="docutils literal">a not in b</tt></td> <td>2.7</td> </tr> <tr class="row-even"><td><a class="reference internal" href="#unittest.TestCase.assertIsInstance" title="unittest.TestCase.assertIsInstance"><tt class="xref py py-meth docutils literal">assertIsInstance(a, b)</tt></a></td> <td><tt class="docutils literal">isinstance(a, b)</tt></td> <td>2.7</td> </tr> <tr class="row-odd"><td><a class="reference internal" href="#unittest.TestCase.assertNotIsInstance" title="unittest.TestCase.assertNotIsInstance"><tt class="xref py py-meth docutils literal">assertNotIsInstance(a, b)</tt></a></td> <td><tt class="docutils literal">not isinstance(a, b)</tt></td> <td>2.7</td> </tr> </tbody> </table> All the assert methods (except <a class="reference internal" href="#unittest.TestCase.assertRaises" title="unittest.TestCase.assertRaises"><tt class="xref py py-meth docutils literal">assertRaises()</tt></a>, <a class="reference internal" href="#unittest.TestCase.assertRaisesRegexp" title="unittest.TestCase.assertRaisesRegexp"><tt class="xref py py-meth docutils literal">assertRaisesRegexp()</tt></a>) accept a msg argument that, if specified, is used as the error message on failure (see also <a class="reference internal" href="#unittest.TestCase.longMessage" title="unittest.TestCase.longMessage"><tt class="xref py py-data docutils literal">longMessage</tt></a>). <dl class="method"> <dt id="unittest.TestCase.assertEqual"> <tt class="descname">assertEqual</tt><big>(</big>first, second, msg=None<big>)</big><a class="headerlink" href="#unittest.TestCase.assertEqual" title="Permalink to this definition">¶</a></dt> <dd>Test that first and second are equal. If the values do not compare equal, the test will fail. In addition, if first and second are the exact same type and one of list, tuple, dict, set, frozenset or unicode or any type that a subclass registers with <a class="reference internal" href="#unittest.TestCase.addTypeEqualityFunc" title="unittest.TestCase.addTypeEqualityFunc"><tt class="xref py py-meth docutils literal">addTypeEqualityFunc()</tt></a> the type-specific equality function will be called in order to generate a more useful default error message (see also the <a class="reference internal" href="#type-specific-methods">list of type-specific methods</a>). Changed in version 2.7: Added the automatic calling of type-specific equality function. </dd></dl> <dl class="method"> <dt id="unittest.TestCase.assertNotEqual"> <tt class="descname">assertNotEqual</tt><big>(</big>first, second, msg=None<big>)</big><a class="headerlink" href="#unittest.TestCase.assertNotEqual" title="Permalink to this definition">¶</a></dt> <dd>Test that first and second are not equal. If the values do compare equal, the test will fail. </dd></dl> <dl class="method"> <dt id="unittest.TestCase.assertTrue"> <tt class="descname">assertTrue</tt><big>(</big>expr, msg=None<big>)</big><a class="headerlink" href="#unittest.TestCase.assertTrue" title="Permalink to this definition">¶</a></dt> <dt id="unittest.TestCase.assertFalse"> <tt class="descname">assertFalse</tt><big>(</big>expr, msg=None<big>)</big><a class="headerlink" href="#unittest.TestCase.assertFalse" title="Permalink to this definition">¶</a></dt> <dd>Test that expr is true (or false). Note that this is equivalent to <tt class="docutils literal">bool(expr) is True</tt> and not to <tt class="docutils literal">expr is True</tt> (use <tt class="docutils literal">assertIs(expr, True)</tt> for the latter). This method should also be avoided when more specific methods are available (e.g. <tt class="docutils literal">assertEqual(a, b)</tt> instead of <tt class="docutils literal">assertTrue(a == b)</tt>), because they provide a better error message in case of failure. </dd></dl> <dl class="method"> <dt id="unittest.TestCase.assertIs"> <tt class="descname">assertIs</tt><big>(</big>first, second, msg=None<big>)</big><a class="headerlink" href="#unittest.TestCase.assertIs" title="Permalink to this definition">¶</a></dt> <dt id="unittest.TestCase.assertIsNot"> <tt class="descname">assertIsNot</tt><big>(</big>first, second, msg=None<big>)</big><a class="headerlink" href="#unittest.TestCase.assertIsNot" title="Permalink to this definition">¶</a></dt> <dd>Test that first and second evaluate (or don’t evaluate) to the same object. New in version 2.7. </dd></dl> <dl class="method"> <dt id="unittest.TestCase.assertIsNone"> <tt class="descname">assertIsNone</tt><big>(</big>expr, msg=None<big>)</big><a class="headerlink" href="#unittest.TestCase.assertIsNone" title="Permalink to this definition">¶</a></dt> <dt id="unittest.TestCase.assertIsNotNone"> <tt class="descname">assertIsNotNone</tt><big>(</big>expr, msg=None<big>)</big><a class="headerlink" href="#unittest.TestCase.assertIsNotNone" title="Permalink to this definition">¶</a></dt> <dd>Test that expr is (or is not) None. New in version 2.7. </dd></dl> <dl class="method"> <dt id="unittest.TestCase.assertIn"> <tt class="descname">assertIn</tt><big>(</big>first, second, msg=None<big>)</big><a class="headerlink" href="#unittest.TestCase.assertIn" title="Permalink to this definition">¶</a></dt> <dt id="unittest.TestCase.assertNotIn"> <tt class="descname">assertNotIn</tt><big>(</big>first, second, msg=None<big>)</big><a class="headerlink" href="#unittest.TestCase.assertNotIn" title="Permalink to this definition">¶</a></dt> <dd>Test that first is (or is not) in second. New in version 2.7. </dd></dl> <dl class="method"> <dt id="unittest.TestCase.assertIsInstance"> <tt class="descname">assertIsInstance</tt><big>(</big>obj, cls, msg=None<big>)</big><a class="headerlink" href="#unittest.TestCase.assertIsInstance" title="Permalink to this definition">¶</a></dt> <dt id="unittest.TestCase.assertNotIsInstance"> <tt class="descname">assertNotIsInstance</tt><big>(</big>obj, cls, msg=None<big>)</big><a class="headerlink" href="#unittest.TestCase.assertNotIsInstance" title="Permalink to this definition">¶</a></dt> <dd>Test that obj is (or is not) an instance of cls (which can be a class or a tuple of classes, as supported by <a class="reference internal" href="functions.html#isinstance" title="isinstance"><tt class="xref py py-func docutils literal">isinstance()</tt></a>). To check for the exact type, use <a class="reference internal" href="#unittest.TestCase.assertIs" title="unittest.TestCase.assertIs"><tt class="xref py py-func docutils literal">assertIs(type(obj), cls)</tt></a>. New in version 2.7. </dd></dl> It is also possible to check that exceptions and warnings are raised using the following methods: <table border="1" class="docutils"> <colgroup> <col width="53%" /> <col width="36%" /> <col width="11%" /> </colgroup> <thead valign="bottom"> <tr class="row-odd"><th class="head">Method</th> <th class="head">Checks that</th> <th class="head">New in</th> </tr> </thead> <tbody valign="top"> <tr class="row-even"><td><a class="reference internal" href="#unittest.TestCase.assertRaises" title="unittest.TestCase.assertRaises"><tt class="xref py py-meth docutils literal">assertRaises(exc, fun, *args, **kwds)</tt></a></td> <td><tt class="docutils literal">fun(*args, **kwds)</tt> raises exc</td> <td> </td> </tr> <tr class="row-odd"><td><a class="reference internal" href="#unittest.TestCase.assertRaisesRegexp" title="unittest.TestCase.assertRaisesRegexp"><tt class="xref py py-meth docutils literal">assertRaisesRegexp(exc, re, fun, *args, **kwds)</tt></a></td> <td><tt class="docutils literal">fun(*args, **kwds)</tt> raises exc and the message matches re</td> <td>2.7</td> </tr> </tbody> </table> <dl class="method"> <dt id="unittest.TestCase.assertRaises"> <tt class="descname">assertRaises</tt><big>(</big>exception, callable, *args, **kwds<big>)</big><a class="headerlink" href="#unittest.TestCase.assertRaises" title="Permalink to this definition">¶</a></dt> <dt> <tt class="descname">assertRaises</tt><big>(</big>exception<big>)</big></dt> <dd>Test that an exception is raised when callable is called with any positional or keyword arguments that are also passed to <a class="reference internal" href="#unittest.TestCase.assertRaises" title="unittest.TestCase.assertRaises"><tt class="xref py py-meth docutils literal">assertRaises()</tt></a>. The test passes if exception is raised, is an error if another exception is raised, or fails if no exception is raised. To catch any of a group of exceptions, a tuple containing the exception classes may be passed as exception. If only the exception argument is given, returns a context manager so that the code under test can be written inline rather than as a function: <div class="highlight-python"><div class="highlight"><pre>with self.assertRaises(SomeException): do_something() </pre></div> </div> The context manager will store the caught exception object in its <tt class="xref py py-attr docutils literal">exception</tt> attribute. This can be useful if the intention is to perform additional checks on the exception raised: <div class="highlight-python"><div class="highlight"><pre>with self.assertRaises(SomeException) as cm: do_something() the_exception = cm.exception self.assertEqual(the_exception.error_code, 3) </pre></div> </div> Changed in version 2.7: Added the ability to use <a class="reference internal" href="#unittest.TestCase.assertRaises" title="unittest.TestCase.assertRaises"><tt class="xref py py-meth docutils literal">assertRaises()</tt></a> as a context manager. </dd></dl> <dl class="method"> <dt id="unittest.TestCase.assertRaisesRegexp"> <tt class="descname">assertRaisesRegexp</tt><big>(</big>exception, regexp, callable, *args, **kwds<big>)</big><a class="headerlink" href="#unittest.TestCase.assertRaisesRegexp" title="Permalink to this definition">¶</a></dt> <dt> <tt class="descname">assertRaisesRegexp</tt><big>(</big>exception, regexp<big>)</big></dt> <dd>Like <a class="reference internal" href="#unittest.TestCase.assertRaises" title="unittest.TestCase.assertRaises"><tt class="xref py py-meth docutils literal">assertRaises()</tt></a> but also tests that regexp matches on the string representation of the raised exception. regexp may be a regular expression object or a string containing a regular expression suitable for use by <a class="reference internal" href="re.html#re.search" title="re.search"><tt class="xref py py-func docutils literal">re.search()</tt></a>. Examples: <div class="highlight-python"><div class="highlight"><pre>self.assertRaisesRegexp(ValueError, 'invalid literal for.*XYZ$', int, 'XYZ') </pre></div> </div> or: <div class="highlight-python"><div class="highlight"><pre>with self.assertRaisesRegexp(ValueError, 'literal'): int('XYZ') </pre></div> </div> New in version 2.7. </dd></dl> There are also other methods used to perform more specific checks, such as: <table border="1" class="docutils"> <colgroup> <col width="46%" /> <col width="38%" /> <col width="16%" /> </colgroup> <thead valign="bottom"> <tr class="row-odd"><th class="head">Method</th> <th class="head">Checks that</th> <th class="head">New in</th> </tr> </thead> <tbody valign="top"> <tr class="row-even"><td><a class="reference internal" href="#unittest.TestCase.assertAlmostEqual" title="unittest.TestCase.assertAlmostEqual"><tt class="xref py py-meth docutils literal">assertAlmostEqual(a, b)</tt></a></td> <td><tt class="docutils literal">round(a-b, 7) == 0</tt></td> <td> </td> </tr> <tr class="row-odd"><td><a class="reference internal" href="#unittest.TestCase.assertNotAlmostEqual" title="unittest.TestCase.assertNotAlmostEqual"><tt class="xref py py-meth docutils literal">assertNotAlmostEqual(a, b)</tt></a></td> <td><tt class="docutils literal">round(a-b, 7) != 0</tt></td> <td> </td> </tr> <tr class="row-even"><td><a class="reference internal" href="#unittest.TestCase.assertGreater" title="unittest.TestCase.assertGreater"><tt class="xref py py-meth docutils literal">assertGreater(a, b)</tt></a></td> <td><tt class="docutils literal">a > b</tt></td> <td>2.7</td> </tr> <tr class="row-odd"><td><a class="reference internal" href="#unittest.TestCase.assertGreaterEqual" title="unittest.TestCase.assertGreaterEqual"><tt class="xref py py-meth docutils literal">assertGreaterEqual(a, b)</tt></a></td> <td><tt class="docutils literal">a >= b</tt></td> <td>2.7</td> </tr> <tr class="row-even"><td><a class="reference internal" href="#unittest.TestCase.assertLess" title="unittest.TestCase.assertLess"><tt class="xref py py-meth docutils literal">assertLess(a, b)</tt></a></td> <td><tt class="docutils literal">a < b</tt></td> <td>2.7</td> </tr> <tr class="row-odd"><td><a class="reference internal" href="#unittest.TestCase.assertLessEqual" title="unittest.TestCase.assertLessEqual"><tt class="xref py py-meth docutils literal">assertLessEqual(a, b)</tt></a></td> <td><tt class="docutils literal">a <= b</tt></td> <td>2.7</td> </tr> <tr class="row-even"><td><a class="reference internal" href="#unittest.TestCase.assertRegexpMatches" title="unittest.TestCase.assertRegexpMatches"><tt class="xref py py-meth docutils literal">assertRegexpMatches(s, re)</tt></a></td> <td><tt class="docutils literal">regex.search(s)</tt></td> <td>2.7</td> </tr> <tr class="row-odd"><td><a class="reference internal" href="#unittest.TestCase.assertNotRegexpMatches" title="unittest.TestCase.assertNotRegexpMatches"><tt class="xref py py-meth docutils literal">assertNotRegexpMatches(s, re)</tt></a></td> <td><tt class="docutils literal">not regex.search(s)</tt></td> <td>2.7</td> </tr> <tr class="row-even"><td><a class="reference internal" href="#unittest.TestCase.assertItemsEqual" title="unittest.TestCase.assertItemsEqual"><tt class="xref py py-meth docutils literal">assertItemsEqual(a, b)</tt></a></td> <td>sorted(a) == sorted(b) and works with unhashable objs</td> <td>2.7</td> </tr> <tr class="row-odd"><td><a class="reference internal" href="#unittest.TestCase.assertDictContainsSubset" title="unittest.TestCase.assertDictContainsSubset"><tt class="xref py py-meth docutils literal">assertDictContainsSubset(a, b)</tt></a></td> <td>all the key/value pairs in a exist in b</td> <td>2.7</td> </tr> </tbody> </table> <dl class="method"> <dt id="unittest.TestCase.assertAlmostEqual"> <tt class="descname">assertAlmostEqual</tt><big>(</big>first, second, places=7, msg=None, delta=None<big>)</big><a class="headerlink" href="#unittest.TestCase.assertAlmostEqual" title="Permalink to this definition">¶</a></dt> <dt id="unittest.TestCase.assertNotAlmostEqual"> <tt class="descname">assertNotAlmostEqual</tt><big>(</big>first, second, places=7, msg=None, delta=None<big>)</big><a class="headerlink" href="#unittest.TestCase.assertNotAlmostEqual" title="Permalink to this definition">¶</a></dt> <dd>Test that first and second are approximately (or not approximately) equal by computing the difference, rounding to the given number of decimal places (default 7), and comparing to zero. Note that these methods round the values to the given number of decimal places (i.e. like the <a class="reference internal" href="functions.html#round" title="round"><tt class="xref py py-func docutils literal">round()</tt></a> function) and not significant digits. If delta is supplied instead of places then the difference between first and second must be less (or more) than delta. Supplying both delta and places raises a <tt class="docutils literal">TypeError</tt>. Changed in version 2.7: <a class="reference internal" href="#unittest.TestCase.assertAlmostEqual" title="unittest.TestCase.assertAlmostEqual"><tt class="xref py py-meth docutils literal">assertAlmostEqual()</tt></a> automatically considers almost equal objects that compare equal. <a class="reference internal" href="#unittest.TestCase.assertNotAlmostEqual" title="unittest.TestCase.assertNotAlmostEqual"><tt class="xref py py-meth docutils literal">assertNotAlmostEqual()</tt></a> automatically fails if the objects compare equal. Added the delta keyword argument. </dd></dl> <dl class="method"> <dt id="unittest.TestCase.assertGreater"> <tt class="descname">assertGreater</tt><big>(</big>first, second, msg=None<big>)</big><a class="headerlink" href="#unittest.TestCase.assertGreater" title="Permalink to this definition">¶</a></dt> <dt id="unittest.TestCase.assertGreaterEqual"> <tt class="descname">assertGreaterEqual</tt><big>(</big>first, second, msg=None<big>)</big><a class="headerlink" href="#unittest.TestCase.assertGreaterEqual" title="Permalink to this definition">¶</a></dt> <dt id="unittest.TestCase.assertLess"> <tt class="descname">assertLess</tt><big>(</big>first, second, msg=None<big>)</big><a class="headerlink" href="#unittest.TestCase.assertLess" title="Permalink to this definition">¶</a></dt> <dt id="unittest.TestCase.assertLessEqual"> <tt class="descname">assertLessEqual</tt><big>(</big>first, second, msg=None<big>)</big><a class="headerlink" href="#unittest.TestCase.assertLessEqual" title="Permalink to this definition">¶</a></dt> <dd>Test that first is respectively >, >=, < or <= than second depending on the method name. If not, the test will fail: <div class="highlight-python"><div class="highlight"><pre>>>> self.assertGreaterEqual(3, 4) AssertionError: "3" unexpectedly not greater than or equal to "4" </pre></div> </div> New in version 2.7. </dd></dl> <dl class="method"> <dt id="unittest.TestCase.assertRegexpMatches"> <tt class="descname">assertRegexpMatches</tt><big>(</big>text, regexp, msg=None<big>)</big><a class="headerlink" href="#unittest.TestCase.assertRegexpMatches" title="Permalink to this definition">¶</a></dt> <dd>Test that a regexp search matches text. In case of failure, the error message will include the pattern and the text (or the pattern and the part of text that unexpectedly matched). regexp may be a regular expression object or a string containing a regular expression suitable for use by <a class="reference internal" href="re.html#re.search" title="re.search"><tt class="xref py py-func docutils literal">re.search()</tt></a>. New in version 2.7. </dd></dl> <dl class="method"> <dt id="unittest.TestCase.assertNotRegexpMatches"> <tt class="descname">assertNotRegexpMatches</tt><big>(</big>text, regexp, msg=None<big>)</big><a class="headerlink" href="#unittest.TestCase.assertNotRegexpMatches" title="Permalink to this definition">¶</a></dt> <dd>Verifies that a regexp search does not match text. Fails with an error message including the pattern and the part of text that matches. regexp may be a regular expression object or a string containing a regular expression suitable for use by <a class="reference internal" href="re.html#re.search" title="re.search"><tt class="xref py py-func docutils literal">re.search()</tt></a>. New in version 2.7. </dd></dl> <dl class="method"> <dt id="unittest.TestCase.assertItemsEqual"> <tt class="descname">assertItemsEqual</tt><big>(</big>actual, expected, msg=None<big>)</big><a class="headerlink" href="#unittest.TestCase.assertItemsEqual" title="Permalink to this definition">¶</a></dt> <dd>Test that sequence expected contains the same elements as actual, regardless of their order. When they don’t, an error message listing the differences between the sequences will be generated. Duplicate elements are not ignored when comparing actual and expected. It verifies if each element has the same count in both sequences. It is the equivalent of <tt class="docutils literal">assertEqual(sorted(expected), sorted(actual))</tt> but it works with sequences of unhashable objects as well. In Python 3, this method is named <tt class="docutils literal">assertCountEqual</tt>. New in version 2.7. </dd></dl> <dl class="method"> <dt id="unittest.TestCase.assertDictContainsSubset"> <tt class="descname">assertDictContainsSubset</tt><big>(</big>expected, actual, msg=None<big>)</big><a class="headerlink" href="#unittest.TestCase.assertDictContainsSubset" title="Permalink to this definition">¶</a></dt> <dd>Tests whether the key/value pairs in dictionary actual are a superset of those in expected. If not, an error message listing the missing keys and mismatched values is generated. New in version 2.7. Deprecated since version 3.2. </dd></dl> The <a class="reference internal" href="#unittest.TestCase.assertEqual" title="unittest.TestCase.assertEqual"><tt class="xref py py-meth docutils literal">assertEqual()</tt></a> method dispatches the equality check for objects of the same type to different type-specific methods. These methods are already implemented for most of the built-in types, but it’s also possible to register new methods using <a class="reference internal" href="#unittest.TestCase.addTypeEqualityFunc" title="unittest.TestCase.addTypeEqualityFunc"><tt class="xref py py-meth docutils literal">addTypeEqualityFunc()</tt></a>: <dl class="method"> <dt id="unittest.TestCase.addTypeEqualityFunc"> <tt class="descname">addTypeEqualityFunc</tt><big>(</big>typeobj, function<big>)</big><a class="headerlink" href="#unittest.TestCase.addTypeEqualityFunc" title="Permalink to this definition">¶</a></dt> <dd>Registers a type-specific method called by <a class="reference internal" href="#unittest.TestCase.assertEqual" title="unittest.TestCase.assertEqual"><tt class="xref py py-meth docutils literal">assertEqual()</tt></a> to check if two objects of exactly the same typeobj (not subclasses) compare equal. function must take two positional arguments and a third msg=None keyword argument just as <a class="reference internal" href="#unittest.TestCase.assertEqual" title="unittest.TestCase.assertEqual"><tt class="xref py py-meth docutils literal">assertEqual()</tt></a> does. It must raise <a class="reference internal" href="#unittest.TestCase.failureException" title="unittest.TestCase.failureException"><tt class="xref py py-data docutils literal">self.failureException(msg)</tt></a> when inequality between the first two parameters is detected – possibly providing useful information and explaining the inequalities in details in the error message. New in version 2.7. </dd></dl> The list of type-specific methods automatically used by <a class="reference internal" href="#unittest.TestCase.assertEqual" title="unittest.TestCase.assertEqual"><tt class="xref py py-meth docutils literal">assertEqual()</tt></a> are summarized in the following table. Note that it’s usually not necessary to invoke these methods directly. <table border="1" class="docutils"> <colgroup> <col width="49%" /> <col width="35%" /> <col width="17%" /> </colgroup> <thead valign="bottom"> <tr class="row-odd"><th class="head">Method</th> <th class="head">Used to compare</th> <th class="head">New in</th> </tr> </thead> <tbody valign="top"> <tr class="row-even"><td><a class="reference internal" href="#unittest.TestCase.assertMultiLineEqual" title="unittest.TestCase.assertMultiLineEqual"><tt class="xref py py-meth docutils literal">assertMultiLineEqual(a, b)</tt></a></td> <td>strings</td> <td>2.7</td> </tr> <tr class="row-odd"><td><a class="reference internal" href="#unittest.TestCase.assertSequenceEqual" title="unittest.TestCase.assertSequenceEqual"><tt class="xref py py-meth docutils literal">assertSequenceEqual(a, b)</tt></a></td> <td>sequences</td> <td>2.7</td> </tr> <tr class="row-even"><td><a class="reference internal" href="#unittest.TestCase.assertListEqual" title="unittest.TestCase.assertListEqual"><tt class="xref py py-meth docutils literal">assertListEqual(a, b)</tt></a></td> <td>lists</td> <td>2.7</td> </tr> <tr class="row-odd"><td><a class="reference internal" href="#unittest.TestCase.assertTupleEqual" title="unittest.TestCase.assertTupleEqual"><tt class="xref py py-meth docutils literal">assertTupleEqual(a, b)</tt></a></td> <td>tuples</td> <td>2.7</td> </tr> <tr class="row-even"><td><a class="reference internal" href="#unittest.TestCase.assertSetEqual" title="unittest.TestCase.assertSetEqual"><tt class="xref py py-meth docutils literal">assertSetEqual(a, b)</tt></a></td> <td>sets or frozensets</td> <td>2.7</td> </tr> <tr class="row-odd"><td><a class="reference internal" href="#unittest.TestCase.assertDictEqual" title="unittest.TestCase.assertDictEqual"><tt class="xref py py-meth docutils literal">assertDictEqual(a, b)</tt></a></td> <td>dicts</td> <td>2.7</td> </tr> </tbody> </table> <dl class="method"> <dt id="unittest.TestCase.assertMultiLineEqual"> <tt class="descname">assertMultiLineEqual</tt><big>(</big>first, second, msg=None<big>)</big><a class="headerlink" href="#unittest.TestCase.assertMultiLineEqual" title="Permalink to this definition">¶</a></dt> <dd>Test that the multiline string first is equal to the string second. When not equal a diff of the two strings highlighting the differences will be included in the error message. This method is used by default when comparing strings with <a class="reference internal" href="#unittest.TestCase.assertEqual" title="unittest.TestCase.assertEqual"><tt class="xref py py-meth docutils literal">assertEqual()</tt></a>. New in version 2.7. </dd></dl> <dl class="method"> <dt id="unittest.TestCase.assertSequenceEqual"> <tt class="descname">assertSequenceEqual</tt><big>(</big>seq1, seq2, msg=None, seq_type=None<big>)</big><a class="headerlink" href="#unittest.TestCase.assertSequenceEqual" title="Permalink to this definition">¶</a></dt> <dd>Tests that two sequences are equal. If a seq_type is supplied, both seq1 and seq2 must be instances of seq_type or a failure will be raised. If the sequences are different an error message is constructed that shows the difference between the two. This method is not called directly by <a class="reference internal" href="#unittest.TestCase.assertEqual" title="unittest.TestCase.assertEqual"><tt class="xref py py-meth docutils literal">assertEqual()</tt></a>, but it’s used to implement <a class="reference internal" href="#unittest.TestCase.assertListEqual" title="unittest.TestCase.assertListEqual"><tt class="xref py py-meth docutils literal">assertListEqual()</tt></a> and <a class="reference internal" href="#unittest.TestCase.assertTupleEqual" title="unittest.TestCase.assertTupleEqual"><tt class="xref py py-meth docutils literal">assertTupleEqual()</tt></a>. New in version 2.7. </dd></dl> <dl class="method"> <dt id="unittest.TestCase.assertListEqual"> <tt class="descname">assertListEqual</tt><big>(</big>list1, list2, msg=None<big>)</big><a class="headerlink" href="#unittest.TestCase.assertListEqual" title="Permalink to this definition">¶</a></dt> <dt id="unittest.TestCase.assertTupleEqual"> <tt class="descname">assertTupleEqual</tt><big>(</big>tuple1, tuple2, msg=None<big>)</big><a class="headerlink" href="#unittest.TestCase.assertTupleEqual" title="Permalink to this definition">¶</a></dt> <dd>Tests that two lists or tuples are equal. If not, an error message is constructed that shows only the differences between the two. An error is also raised if either of the parameters are of the wrong type. These methods are used by default when comparing lists or tuples with <a class="reference internal" href="#unittest.TestCase.assertEqual" title="unittest.TestCase.assertEqual"><tt class="xref py py-meth docutils literal">assertEqual()</tt></a>. New in version 2.7. </dd></dl> <dl class="method"> <dt id="unittest.TestCase.assertSetEqual"> <tt class="descname">assertSetEqual</tt><big>(</big>set1, set2, msg=None<big>)</big><a class="headerlink" href="#unittest.TestCase.assertSetEqual" title="Permalink to this definition">¶</a></dt> <dd>Tests that two sets are equal. If not, an error message is constructed that lists the differences between the sets. This method is used by default when comparing sets or frozensets with <a class="reference internal" href="#unittest.TestCase.assertEqual" title="unittest.TestCase.assertEqual"><tt class="xref py py-meth docutils literal">assertEqual()</tt></a>. Fails if either of set1 or set2 does not have a <a class="reference internal" href="stdtypes.html#set.difference" title="set.difference"><tt class="xref py py-meth docutils literal">set.difference()</tt></a> method. New in version 2.7. </dd></dl> <dl class="method"> <dt id="unittest.TestCase.assertDictEqual"> <tt class="descname">assertDictEqual</tt><big>(</big>expected, actual, msg=None<big>)</big><a class="headerlink" href="#unittest.TestCase.assertDictEqual" title="Permalink to this definition">¶</a></dt> <dd>Test that two dictionaries are equal. If not, an error message is constructed that shows the differences in the dictionaries. This method will be used by default to compare dictionaries in calls to <a class="reference internal" href="#unittest.TestCase.assertEqual" title="unittest.TestCase.assertEqual"><tt class="xref py py-meth docutils literal">assertEqual()</tt></a>. New in version 2.7. </dd></dl> Finally the <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> provides the following methods and attributes: <dl class="method"> <dt id="unittest.TestCase.fail"> <tt class="descname">fail</tt><big>(</big>msg=None<big>)</big><a class="headerlink" href="#unittest.TestCase.fail" title="Permalink to this definition">¶</a></dt> <dd>Signals a test failure unconditionally, with msg or <tt class="docutils literal">None</tt> for the error message. </dd></dl> <dl class="attribute"> <dt id="unittest.TestCase.failureException"> <tt class="descname">failureException</tt><a class="headerlink" href="#unittest.TestCase.failureException" title="Permalink to this definition">¶</a></dt> <dd>This class attribute gives the exception raised by the test method. If a test framework needs to use a specialized exception, possibly to carry additional information, it must subclass this exception in order to “play fair” with the framework. The initial value of this attribute is <a class="reference internal" href="exceptions.html#exceptions.AssertionError" title="exceptions.AssertionError"><tt class="xref py py-exc docutils literal">AssertionError</tt></a>. </dd></dl> <dl class="attribute"> <dt id="unittest.TestCase.longMessage"> <tt class="descname">longMessage</tt><a class="headerlink" href="#unittest.TestCase.longMessage" title="Permalink to this definition">¶</a></dt> <dd>If set to <tt class="docutils literal">True</tt> then any explicit failure message you pass in to the <a class="reference internal" href="#assert-methods">assert methods</a> will be appended to the end of the normal failure message. The normal messages contain useful information about the objects involved, for example the message from assertEqual shows you the repr of the two unequal objects. Setting this attribute to <tt class="docutils literal">True</tt> allows you to have a custom error message in addition to the normal one. This attribute defaults to <tt class="docutils literal">False</tt>, meaning that a custom message passed to an assert method will silence the normal message. The class setting can be overridden in individual tests by assigning an instance attribute to <tt class="docutils literal">True</tt> or <tt class="docutils literal">False</tt> before calling the assert methods. New in version 2.7. </dd></dl> <dl class="attribute"> <dt id="unittest.TestCase.maxDiff"> <tt class="descname">maxDiff</tt><a class="headerlink" href="#unittest.TestCase.maxDiff" title="Permalink to this definition">¶</a></dt> <dd>This attribute controls the maximum length of diffs output by assert methods that report diffs on failure. It defaults to 80*8 characters. Assert methods affected by this attribute are <a class="reference internal" href="#unittest.TestCase.assertSequenceEqual" title="unittest.TestCase.assertSequenceEqual"><tt class="xref py py-meth docutils literal">assertSequenceEqual()</tt></a> (including all the sequence comparison methods that delegate to it), <a class="reference internal" href="#unittest.TestCase.assertDictEqual" title="unittest.TestCase.assertDictEqual"><tt class="xref py py-meth docutils literal">assertDictEqual()</tt></a> and <a class="reference internal" href="#unittest.TestCase.assertMultiLineEqual" title="unittest.TestCase.assertMultiLineEqual"><tt class="xref py py-meth docutils literal">assertMultiLineEqual()</tt></a>. Setting <tt class="docutils literal">maxDiff</tt> to None means that there is no maximum length of diffs. New in version 2.7. </dd></dl> Testing frameworks can use the following methods to collect information on the test: <dl class="method"> <dt id="unittest.TestCase.countTestCases"> <tt class="descname">countTestCases</tt><big>(</big><big>)</big><a class="headerlink" href="#unittest.TestCase.countTestCases" title="Permalink to this definition">¶</a></dt> <dd>Return the number of tests represented by this test object. For <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> instances, this will always be <tt class="docutils literal">1</tt>. </dd></dl> <dl class="method"> <dt id="unittest.TestCase.defaultTestResult"> <tt class="descname">defaultTestResult</tt><big>(</big><big>)</big><a class="headerlink" href="#unittest.TestCase.defaultTestResult" title="Permalink to this definition">¶</a></dt> <dd>Return an instance of the test result class that should be used for this test case class (if no other result instance is provided to the <a class="reference internal" href="#unittest.TestCase.run" title="unittest.TestCase.run"><tt class="xref py py-meth docutils literal">run()</tt></a> method). For <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> instances, this will always be an instance of <a class="reference internal" href="#unittest.TestResult" title="unittest.TestResult"><tt class="xref py py-class docutils literal">TestResult</tt></a>; subclasses of <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> should override this as necessary. </dd></dl> <dl class="method"> <dt id="unittest.TestCase.id"> <tt class="descname">id</tt><big>(</big><big>)</big><a class="headerlink" href="#unittest.TestCase.id" title="Permalink to this definition">¶</a></dt> <dd>Return a string identifying the specific test case. This is usually the full name of the test method, including the module and class name. </dd></dl> <dl class="method"> <dt id="unittest.TestCase.shortDescription"> <tt class="descname">shortDescription</tt><big>(</big><big>)</big><a class="headerlink" href="#unittest.TestCase.shortDescription" title="Permalink to this definition">¶</a></dt> <dd>Returns a description of the test, or <tt class="docutils literal">None</tt> if no description has been provided. The default implementation of this method returns the first line of the test method’s docstring, if available, or <a class="reference internal" href="constants.html#None" title="None"><tt class="xref py py-const docutils literal">None</tt></a>. </dd></dl> <dl class="method"> <dt id="unittest.TestCase.addCleanup"> <tt class="descname">addCleanup</tt><big>(</big>function, *args, **kwargs<big>)</big><a class="headerlink" href="#unittest.TestCase.addCleanup" title="Permalink to this definition">¶</a></dt> <dd>Add a function to be called after <a class="reference internal" href="#unittest.TestCase.tearDown" title="unittest.TestCase.tearDown"><tt class="xref py py-meth docutils literal">tearDown()</tt></a> to cleanup resources used during the test. Functions will be called in reverse order to the order they are added (LIFO). They are called with any arguments and keyword arguments passed into <a class="reference internal" href="#unittest.TestCase.addCleanup" title="unittest.TestCase.addCleanup"><tt class="xref py py-meth docutils literal">addCleanup()</tt></a> when they are added. If <a class="reference internal" href="#unittest.TestCase.setUp" title="unittest.TestCase.setUp"><tt class="xref py py-meth docutils literal">setUp()</tt></a> fails, meaning that <a class="reference internal" href="#unittest.TestCase.tearDown" title="unittest.TestCase.tearDown"><tt class="xref py py-meth docutils literal">tearDown()</tt></a> is not called, then any cleanup functions added will still be called. New in version 2.7. </dd></dl> <dl class="method"> <dt id="unittest.TestCase.doCleanups"> <tt class="descname">doCleanups</tt><big>(</big><big>)</big><a class="headerlink" href="#unittest.TestCase.doCleanups" title="Permalink to this definition">¶</a></dt> <dd>This method is called unconditionally after <a class="reference internal" href="#unittest.TestCase.tearDown" title="unittest.TestCase.tearDown"><tt class="xref py py-meth docutils literal">tearDown()</tt></a>, or after <a class="reference internal" href="#unittest.TestCase.setUp" title="unittest.TestCase.setUp"><tt class="xref py py-meth docutils literal">setUp()</tt></a> if <a class="reference internal" href="#unittest.TestCase.setUp" title="unittest.TestCase.setUp"><tt class="xref py py-meth docutils literal">setUp()</tt></a> raises an exception. It is responsible for calling all the cleanup functions added by <a class="reference internal" href="#unittest.TestCase.addCleanup" title="unittest.TestCase.addCleanup"><tt class="xref py py-meth docutils literal">addCleanup()</tt></a>. If you need cleanup functions to be called prior to <a class="reference internal" href="#unittest.TestCase.tearDown" title="unittest.TestCase.tearDown"><tt class="xref py py-meth docutils literal">tearDown()</tt></a> then you can call <a class="reference internal" href="#unittest.TestCase.doCleanups" title="unittest.TestCase.doCleanups"><tt class="xref py py-meth docutils literal">doCleanups()</tt></a> yourself. <a class="reference internal" href="#unittest.TestCase.doCleanups" title="unittest.TestCase.doCleanups"><tt class="xref py py-meth docutils literal">doCleanups()</tt></a> pops methods off the stack of cleanup functions one at a time, so it can be called at any time. New in version 2.7. </dd></dl> </dd></dl> <dl class="class"> <dt id="unittest.FunctionTestCase"> class <tt class="descclassname">unittest.</tt><tt class="descname">FunctionTestCase</tt><big>(</big>testFunc, setUp=None, tearDown=None, description=None<big>)</big><a class="headerlink" href="#unittest.FunctionTestCase" title="Permalink to this definition">¶</a></dt> <dd>This class implements the portion of the <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> interface which allows the test runner to drive the test, but does not provide the methods which test code can use to check and report errors. This is used to create test cases using legacy test code, allowing it to be integrated into a <a class="reference internal" href="#module-unittest" title="unittest: Unit testing framework for Python."><tt class="xref py py-mod docutils literal">unittest</tt></a>-based test framework. </dd></dl> <div class="section" id="deprecated-aliases"> <h4>25.3.7.1.1. Deprecated aliases<a class="headerlink" href="#deprecated-aliases" title="Permalink to this headline">¶</a></h4> For historical reasons, some of the <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> methods had one or more aliases that are now deprecated. The following table lists the correct names along with their deprecated aliases: <blockquote> <div><table border="1" class="docutils"> <colgroup> <col width="49%" /> <col width="51%" /> </colgroup> <thead valign="bottom"> <tr class="row-odd"><th class="head">Method Name</th> <th class="head">Deprecated alias(es)</th> </tr> </thead> <tbody valign="top"> <tr class="row-even"><td><a class="reference internal" href="#unittest.TestCase.assertEqual" title="unittest.TestCase.assertEqual"><tt class="xref py py-meth docutils literal">assertEqual()</tt></a></td> <td>failUnlessEqual, assertEquals</td> </tr> <tr class="row-odd"><td><a class="reference internal" href="#unittest.TestCase.assertNotEqual" title="unittest.TestCase.assertNotEqual"><tt class="xref py py-meth docutils literal">assertNotEqual()</tt></a></td> <td>failIfEqual</td> </tr> <tr class="row-even"><td><a class="reference internal" href="#unittest.TestCase.assertTrue" title="unittest.TestCase.assertTrue"><tt class="xref py py-meth docutils literal">assertTrue()</tt></a></td> <td>failUnless, assert_</td> </tr> <tr class="row-odd"><td><a class="reference internal" href="#unittest.TestCase.assertFalse" title="unittest.TestCase.assertFalse"><tt class="xref py py-meth docutils literal">assertFalse()</tt></a></td> <td>failIf</td> </tr> <tr class="row-even"><td><a class="reference internal" href="#unittest.TestCase.assertRaises" title="unittest.TestCase.assertRaises"><tt class="xref py py-meth docutils literal">assertRaises()</tt></a></td> <td>failUnlessRaises</td> </tr> <tr class="row-odd"><td><a class="reference internal" href="#unittest.TestCase.assertAlmostEqual" title="unittest.TestCase.assertAlmostEqual"><tt class="xref py py-meth docutils literal">assertAlmostEqual()</tt></a></td> <td>failUnlessAlmostEqual</td> </tr> <tr class="row-even"><td><a class="reference internal" href="#unittest.TestCase.assertNotAlmostEqual" title="unittest.TestCase.assertNotAlmostEqual"><tt class="xref py py-meth docutils literal">assertNotAlmostEqual()</tt></a></td> <td>failIfAlmostEqual</td> </tr> </tbody> </table> Deprecated since version 2.7: the aliases listed in the second column </div></blockquote> </div> </div> <div class="section" id="grouping-tests"> <h3>25.3.7.2. Grouping tests<a class="headerlink" href="#grouping-tests" title="Permalink to this headline">¶</a></h3> <dl class="class"> <dt id="unittest.TestSuite"> class <tt class="descclassname">unittest.</tt><tt class="descname">TestSuite</tt><big>(</big>tests=()<big>)</big><a class="headerlink" href="#unittest.TestSuite" title="Permalink to this definition">¶</a></dt> <dd>This class represents an aggregation of individual tests cases and test suites. The class presents the interface needed by the test runner to allow it to be run as any other test case. Running a <a class="reference internal" href="#unittest.TestSuite" title="unittest.TestSuite"><tt class="xref py py-class docutils literal">TestSuite</tt></a> instance is the same as iterating over the suite, running each test individually. If tests is given, it must be an iterable of individual test cases or other test suites that will be used to build the suite initially. Additional methods are provided to add test cases and suites to the collection later on. <a class="reference internal" href="#unittest.TestSuite" title="unittest.TestSuite"><tt class="xref py py-class docutils literal">TestSuite</tt></a> objects behave much like <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> objects, except they do not actually implement a test. Instead, they are used to aggregate tests into groups of tests that should be run together. Some additional methods are available to add tests to <a class="reference internal" href="#unittest.TestSuite" title="unittest.TestSuite"><tt class="xref py py-class docutils literal">TestSuite</tt></a> instances: <dl class="method"> <dt id="unittest.TestSuite.addTest"> <tt class="descname">addTest</tt><big>(</big>test<big>)</big><a class="headerlink" href="#unittest.TestSuite.addTest" title="Permalink to this definition">¶</a></dt> <dd>Add a <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> or <a class="reference internal" href="#unittest.TestSuite" title="unittest.TestSuite"><tt class="xref py py-class docutils literal">TestSuite</tt></a> to the suite. </dd></dl> <dl class="method"> <dt id="unittest.TestSuite.addTests"> <tt class="descname">addTests</tt><big>(</big>tests<big>)</big><a class="headerlink" href="#unittest.TestSuite.addTests" title="Permalink to this definition">¶</a></dt> <dd>Add all the tests from an iterable of <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> and <a class="reference internal" href="#unittest.TestSuite" title="unittest.TestSuite"><tt class="xref py py-class docutils literal">TestSuite</tt></a> instances to this test suite. This is equivalent to iterating over tests, calling <a class="reference internal" href="#unittest.TestSuite.addTest" title="unittest.TestSuite.addTest"><tt class="xref py py-meth docutils literal">addTest()</tt></a> for each element. </dd></dl> <a class="reference internal" href="#unittest.TestSuite" title="unittest.TestSuite"><tt class="xref py py-class docutils literal">TestSuite</tt></a> shares the following methods with <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a>: <dl class="method"> <dt id="unittest.TestSuite.run"> <tt class="descname">run</tt><big>(</big>result<big>)</big><a class="headerlink" href="#unittest.TestSuite.run" title="Permalink to this definition">¶</a></dt> <dd>Run the tests associated with this suite, collecting the result into the test result object passed as result. Note that unlike <a class="reference internal" href="#unittest.TestCase.run" title="unittest.TestCase.run"><tt class="xref py py-meth docutils literal">TestCase.run()</tt></a>, <a class="reference internal" href="#unittest.TestSuite.run" title="unittest.TestSuite.run"><tt class="xref py py-meth docutils literal">TestSuite.run()</tt></a> requires the result object to be passed in. </dd></dl> <dl class="method"> <dt id="unittest.TestSuite.debug"> <tt class="descname">debug</tt><big>(</big><big>)</big><a class="headerlink" href="#unittest.TestSuite.debug" title="Permalink to this definition">¶</a></dt> <dd>Run the tests associated with this suite without collecting the result. This allows exceptions raised by the test to be propagated to the caller and can be used to support running tests under a debugger. </dd></dl> <dl class="method"> <dt id="unittest.TestSuite.countTestCases"> <tt class="descname">countTestCases</tt><big>(</big><big>)</big><a class="headerlink" href="#unittest.TestSuite.countTestCases" title="Permalink to this definition">¶</a></dt> <dd>Return the number of tests represented by this test object, including all individual tests and sub-suites. </dd></dl> <dl class="method"> <dt id="unittest.TestSuite.__iter__"> <tt class="descname">__iter__</tt><big>(</big><big>)</big><a class="headerlink" href="#unittest.TestSuite.__iter__" title="Permalink to this definition">¶</a></dt> <dd>Tests grouped by a <a class="reference internal" href="#unittest.TestSuite" title="unittest.TestSuite"><tt class="xref py py-class docutils literal">TestSuite</tt></a> are always accessed by iteration. Subclasses can lazily provide tests by overriding <a class="reference internal" href="#unittest.TestSuite.__iter__" title="unittest.TestSuite.__iter__"><tt class="xref py py-meth docutils literal">__iter__()</tt></a>. Note that this method maybe called several times on a single suite (for example when counting tests or comparing for equality) so the tests returned must be the same for repeated iterations. Changed in version 2.7: In earlier versions the <a class="reference internal" href="#unittest.TestSuite" title="unittest.TestSuite"><tt class="xref py py-class docutils literal">TestSuite</tt></a> accessed tests directly rather than through iteration, so overriding <a class="reference internal" href="#unittest.TestSuite.__iter__" title="unittest.TestSuite.__iter__"><tt class="xref py py-meth docutils literal">__iter__()</tt></a> wasn’t sufficient for providing tests. </dd></dl> In the typical usage of a <a class="reference internal" href="#unittest.TestSuite" title="unittest.TestSuite"><tt class="xref py py-class docutils literal">TestSuite</tt></a> object, the <a class="reference internal" href="#unittest.TestSuite.run" title="unittest.TestSuite.run"><tt class="xref py py-meth docutils literal">run()</tt></a> method is invoked by a <tt class="xref py py-class docutils literal">TestRunner</tt> rather than by the end-user test harness. </dd></dl> </div> <div class="section" id="loading-and-running-tests"> <h3>25.3.7.3. Loading and running tests<a class="headerlink" href="#loading-and-running-tests" title="Permalink to this headline">¶</a></h3> <dl class="class"> <dt id="unittest.TestLoader"> class <tt class="descclassname">unittest.</tt><tt class="descname">TestLoader</tt><a class="headerlink" href="#unittest.TestLoader" title="Permalink to this definition">¶</a></dt> <dd>The <a class="reference internal" href="#unittest.TestLoader" title="unittest.TestLoader"><tt class="xref py py-class docutils literal">TestLoader</tt></a> class is used to create test suites from classes and modules. Normally, there is no need to create an instance of this class; the <a class="reference internal" href="#module-unittest" title="unittest: Unit testing framework for Python."><tt class="xref py py-mod docutils literal">unittest</tt></a> module provides an instance that can be shared as <a class="reference internal" href="#unittest.defaultTestLoader" title="unittest.defaultTestLoader"><tt class="xref py py-data docutils literal">unittest.defaultTestLoader</tt></a>. Using a subclass or instance, however, allows customization of some configurable properties. <a class="reference internal" href="#unittest.TestLoader" title="unittest.TestLoader"><tt class="xref py py-class docutils literal">TestLoader</tt></a> objects have the following methods: <dl class="method"> <dt id="unittest.TestLoader.loadTestsFromTestCase"> <tt class="descname">loadTestsFromTestCase</tt><big>(</big>testCaseClass<big>)</big><a class="headerlink" href="#unittest.TestLoader.loadTestsFromTestCase" title="Permalink to this definition">¶</a></dt> <dd>Return a suite of all tests cases contained in the <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a>-derived <tt class="xref py py-class docutils literal">testCaseClass</tt>. </dd></dl> <dl class="method"> <dt id="unittest.TestLoader.loadTestsFromModule"> <tt class="descname">loadTestsFromModule</tt><big>(</big>module<big>)</big><a class="headerlink" href="#unittest.TestLoader.loadTestsFromModule" title="Permalink to this definition">¶</a></dt> <dd>Return a suite of all tests cases contained in the given module. This method searches module for classes derived from <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> and creates an instance of the class for each test method defined for the class. <div class="admonition note"> Note While using a hierarchy of <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a>-derived classes can be convenient in sharing fixtures and helper functions, defining test methods on base classes that are not intended to be instantiated directly does not play well with this method. Doing so, however, can be useful when the fixtures are different and defined in subclasses. </div> If a module provides a <tt class="docutils literal">load_tests</tt> function it will be called to load the tests. This allows modules to customize test loading. This is the <a class="reference internal" href="#load-tests-protocol">load_tests protocol</a>. Changed in version 2.7: Support for <tt class="docutils literal">load_tests</tt> added. </dd></dl> <dl class="method"> <dt id="unittest.TestLoader.loadTestsFromName"> <tt class="descname">loadTestsFromName</tt><big>(</big>name, module=None<big>)</big><a class="headerlink" href="#unittest.TestLoader.loadTestsFromName" title="Permalink to this definition">¶</a></dt> <dd>Return a suite of all tests cases given a string specifier. The specifier name is a “dotted name” that may resolve either to a module, a test case class, a test method within a test case class, a <a class="reference internal" href="#unittest.TestSuite" title="unittest.TestSuite"><tt class="xref py py-class docutils literal">TestSuite</tt></a> instance, or a callable object which returns a <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> or <a class="reference internal" href="#unittest.TestSuite" title="unittest.TestSuite"><tt class="xref py py-class docutils literal">TestSuite</tt></a> instance. These checks are applied in the order listed here; that is, a method on a possible test case class will be picked up as “a test method within a test case class”, rather than “a callable object”. For example, if you have a module <tt class="xref py py-mod docutils literal">SampleTests</tt> containing a <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a>-derived class <tt class="xref py py-class docutils literal">SampleTestCase</tt> with three test methods (<tt class="xref py py-meth docutils literal">test_one()</tt>, <tt class="xref py py-meth docutils literal">test_two()</tt>, and <tt class="xref py py-meth docutils literal">test_three()</tt>), the specifier <tt class="docutils literal">'SampleTests.SampleTestCase'</tt> would cause this method to return a suite which will run all three test methods. Using the specifier <tt class="docutils literal">'SampleTests.SampleTestCase.test_two'</tt> would cause it to return a test suite which will run only the <tt class="xref py py-meth docutils literal">test_two()</tt> test method. The specifier can refer to modules and packages which have not been imported; they will be imported as a side-effect. The method optionally resolves name relative to the given module. </dd></dl> <dl class="method"> <dt id="unittest.TestLoader.loadTestsFromNames"> <tt class="descname">loadTestsFromNames</tt><big>(</big>names, module=None<big>)</big><a class="headerlink" href="#unittest.TestLoader.loadTestsFromNames" title="Permalink to this definition">¶</a></dt> <dd>Similar to <a class="reference internal" href="#unittest.TestLoader.loadTestsFromName" title="unittest.TestLoader.loadTestsFromName"><tt class="xref py py-meth docutils literal">loadTestsFromName()</tt></a>, but takes a sequence of names rather than a single name. The return value is a test suite which supports all the tests defined for each name. </dd></dl> <dl class="method"> <dt id="unittest.TestLoader.getTestCaseNames"> <tt class="descname">getTestCaseNames</tt><big>(</big>testCaseClass<big>)</big><a class="headerlink" href="#unittest.TestLoader.getTestCaseNames" title="Permalink to this definition">¶</a></dt> <dd>Return a sorted sequence of method names found within testCaseClass; this should be a subclass of <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a>. </dd></dl> <dl class="method"> <dt id="unittest.TestLoader.discover"> <tt class="descname">discover</tt><big>(</big>start_dir, pattern='test*.py', top_level_dir=None<big>)</big><a class="headerlink" href="#unittest.TestLoader.discover" title="Permalink to this definition">¶</a></dt> <dd>Find and return all test modules from the specified start directory, recursing into subdirectories to find them. Only test files that match pattern will be loaded. (Using shell style pattern matching.) Only module names that are importable (i.e. are valid Python identifiers) will be loaded. All test modules must be importable from the top level of the project. If the start directory is not the top level directory then the top level directory must be specified separately. If importing a module fails, for example due to a syntax error, then this will be recorded as a single error and discovery will continue. If a test package name (directory with <tt class="file docutils literal">__init__.py</tt>) matches the pattern then the package will be checked for a <tt class="docutils literal">load_tests</tt> function. If this exists then it will be called with loader, tests, pattern. If load_tests exists then discovery does not recurse into the package, <tt class="docutils literal">load_tests</tt> is responsible for loading all tests in the package. The pattern is deliberately not stored as a loader attribute so that packages can continue discovery themselves. top_level_dir is stored so <tt class="docutils literal">load_tests</tt> does not need to pass this argument in to <tt class="docutils literal">loader.discover()</tt>. start_dir can be a dotted module name as well as a directory. New in version 2.7. </dd></dl> The following attributes of a <a class="reference internal" href="#unittest.TestLoader" title="unittest.TestLoader"><tt class="xref py py-class docutils literal">TestLoader</tt></a> can be configured either by subclassing or assignment on an instance: <dl class="attribute"> <dt id="unittest.TestLoader.testMethodPrefix"> <tt class="descname">testMethodPrefix</tt><a class="headerlink" href="#unittest.TestLoader.testMethodPrefix" title="Permalink to this definition">¶</a></dt> <dd>String giving the prefix of method names which will be interpreted as test methods. The default value is <tt class="docutils literal">'test'</tt>. This affects <a class="reference internal" href="#unittest.TestLoader.getTestCaseNames" title="unittest.TestLoader.getTestCaseNames"><tt class="xref py py-meth docutils literal">getTestCaseNames()</tt></a> and all the <tt class="xref py py-meth docutils literal">loadTestsFrom*()</tt> methods. </dd></dl> <dl class="attribute"> <dt id="unittest.TestLoader.sortTestMethodsUsing"> <tt class="descname">sortTestMethodsUsing</tt><a class="headerlink" href="#unittest.TestLoader.sortTestMethodsUsing" title="Permalink to this definition">¶</a></dt> <dd>Function to be used to compare method names when sorting them in <a class="reference internal" href="#unittest.TestLoader.getTestCaseNames" title="unittest.TestLoader.getTestCaseNames"><tt class="xref py py-meth docutils literal">getTestCaseNames()</tt></a> and all the <tt class="xref py py-meth docutils literal">loadTestsFrom*()</tt> methods. The default value is the built-in <a class="reference internal" href="functions.html#cmp" title="cmp"><tt class="xref py py-func docutils literal">cmp()</tt></a> function; the attribute can also be set to <a class="reference internal" href="constants.html#None" title="None"><tt class="xref py py-const docutils literal">None</tt></a> to disable the sort. </dd></dl> <dl class="attribute"> <dt id="unittest.TestLoader.suiteClass"> <tt class="descname">suiteClass</tt><a class="headerlink" href="#unittest.TestLoader.suiteClass" title="Permalink to this definition">¶</a></dt> <dd>Callable object that constructs a test suite from a list of tests. No methods on the resulting object are needed. The default value is the <a class="reference internal" href="#unittest.TestSuite" title="unittest.TestSuite"><tt class="xref py py-class docutils literal">TestSuite</tt></a> class. This affects all the <tt class="xref py py-meth docutils literal">loadTestsFrom*()</tt> methods. </dd></dl> </dd></dl> <dl class="class"> <dt id="unittest.TestResult"> class <tt class="descclassname">unittest.</tt><tt class="descname">TestResult</tt><a class="headerlink" href="#unittest.TestResult" title="Permalink to this definition">¶</a></dt> <dd>This class is used to compile information about which tests have succeeded and which have failed. A <a class="reference internal" href="#unittest.TestResult" title="unittest.TestResult"><tt class="xref py py-class docutils literal">TestResult</tt></a> object stores the results of a set of tests. The <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> and <a class="reference internal" href="#unittest.TestSuite" title="unittest.TestSuite"><tt class="xref py py-class docutils literal">TestSuite</tt></a> classes ensure that results are properly recorded; test authors do not need to worry about recording the outcome of tests. Testing frameworks built on top of <a class="reference internal" href="#module-unittest" title="unittest: Unit testing framework for Python."><tt class="xref py py-mod docutils literal">unittest</tt></a> may want access to the <a class="reference internal" href="#unittest.TestResult" title="unittest.TestResult"><tt class="xref py py-class docutils literal">TestResult</tt></a> object generated by running a set of tests for reporting purposes; a <a class="reference internal" href="#unittest.TestResult" title="unittest.TestResult"><tt class="xref py py-class docutils literal">TestResult</tt></a> instance is returned by the <tt class="xref py py-meth docutils literal">TestRunner.run()</tt> method for this purpose. <a class="reference internal" href="#unittest.TestResult" title="unittest.TestResult"><tt class="xref py py-class docutils literal">TestResult</tt></a> instances have the following attributes that will be of interest when inspecting the results of running a set of tests: <dl class="attribute"> <dt id="unittest.TestResult.errors"> <tt class="descname">errors</tt><a class="headerlink" href="#unittest.TestResult.errors" title="Permalink to this definition">¶</a></dt> <dd>A list containing 2-tuples of <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> instances and strings holding formatted tracebacks. Each tuple represents a test which raised an unexpected exception. Changed in version 2.2: Contains formatted tracebacks instead of <a class="reference internal" href="sys.html#sys.exc_info" title="sys.exc_info"><tt class="xref py py-func docutils literal">sys.exc_info()</tt></a> results. </dd></dl> <dl class="attribute"> <dt id="unittest.TestResult.failures"> <tt class="descname">failures</tt><a class="headerlink" href="#unittest.TestResult.failures" title="Permalink to this definition">¶</a></dt> <dd>A list containing 2-tuples of <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> instances and strings holding formatted tracebacks. Each tuple represents a test where a failure was explicitly signalled using the <tt class="xref py py-meth docutils literal">TestCase.fail*()</tt> or <tt class="xref py py-meth docutils literal">TestCase.assert*()</tt> methods. Changed in version 2.2: Contains formatted tracebacks instead of <a class="reference internal" href="sys.html#sys.exc_info" title="sys.exc_info"><tt class="xref py py-func docutils literal">sys.exc_info()</tt></a> results. </dd></dl> <dl class="attribute"> <dt id="unittest.TestResult.skipped"> <tt class="descname">skipped</tt><a class="headerlink" href="#unittest.TestResult.skipped" title="Permalink to this definition">¶</a></dt> <dd>A list containing 2-tuples of <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> instances and strings holding the reason for skipping the test. New in version 2.7. </dd></dl> <dl class="attribute"> <dt id="unittest.TestResult.expectedFailures"> <tt class="descname">expectedFailures</tt><a class="headerlink" href="#unittest.TestResult.expectedFailures" title="Permalink to this definition">¶</a></dt> <dd>A list containing 2-tuples of <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> instances and strings holding formatted tracebacks. Each tuple represents an expected failure of the test case. </dd></dl> <dl class="attribute"> <dt id="unittest.TestResult.unexpectedSuccesses"> <tt class="descname">unexpectedSuccesses</tt><a class="headerlink" href="#unittest.TestResult.unexpectedSuccesses" title="Permalink to this definition">¶</a></dt> <dd>A list containing <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> instances that were marked as expected failures, but succeeded. </dd></dl> <dl class="attribute"> <dt id="unittest.TestResult.shouldStop"> <tt class="descname">shouldStop</tt><a class="headerlink" href="#unittest.TestResult.shouldStop" title="Permalink to this definition">¶</a></dt> <dd>Set to <tt class="docutils literal">True</tt> when the execution of tests should stop by <a class="reference internal" href="#unittest.TestResult.stop" title="unittest.TestResult.stop"><tt class="xref py py-meth docutils literal">stop()</tt></a>. </dd></dl> <dl class="attribute"> <dt id="unittest.TestResult.testsRun"> <tt class="descname">testsRun</tt><a class="headerlink" href="#unittest.TestResult.testsRun" title="Permalink to this definition">¶</a></dt> <dd>The total number of tests run so far. </dd></dl> <dl class="attribute"> <dt id="unittest.TestResult.buffer"> <tt class="descname">buffer</tt><a class="headerlink" href="#unittest.TestResult.buffer" title="Permalink to this definition">¶</a></dt> <dd>If set to true, <tt class="docutils literal">sys.stdout</tt> and <tt class="docutils literal">sys.stderr</tt> will be buffered in between <a class="reference internal" href="#unittest.TestResult.startTest" title="unittest.TestResult.startTest"><tt class="xref py py-meth docutils literal">startTest()</tt></a> and <a class="reference internal" href="#unittest.TestResult.stopTest" title="unittest.TestResult.stopTest"><tt class="xref py py-meth docutils literal">stopTest()</tt></a> being called. Collected output will only be echoed onto the real <tt class="docutils literal">sys.stdout</tt> and <tt class="docutils literal">sys.stderr</tt> if the test fails or errors. Any output is also attached to the failure / error message. New in version 2.7. </dd></dl> <dl class="attribute"> <dt id="unittest.TestResult.failfast"> <tt class="descname">failfast</tt><a class="headerlink" href="#unittest.TestResult.failfast" title="Permalink to this definition">¶</a></dt> <dd>If set to true <a class="reference internal" href="#unittest.TestResult.stop" title="unittest.TestResult.stop"><tt class="xref py py-meth docutils literal">stop()</tt></a> will be called on the first failure or error, halting the test run. New in version 2.7. </dd></dl> <dl class="method"> <dt id="unittest.TestResult.wasSuccessful"> <tt class="descname">wasSuccessful</tt><big>(</big><big>)</big><a class="headerlink" href="#unittest.TestResult.wasSuccessful" title="Permalink to this definition">¶</a></dt> <dd>Return <tt class="docutils literal">True</tt> if all tests run so far have passed, otherwise returns <tt class="docutils literal">False</tt>. </dd></dl> <dl class="method"> <dt id="unittest.TestResult.stop"> <tt class="descname">stop</tt><big>(</big><big>)</big><a class="headerlink" href="#unittest.TestResult.stop" title="Permalink to this definition">¶</a></dt> <dd>This method can be called to signal that the set of tests being run should be aborted by setting the <a class="reference internal" href="#unittest.TestResult.shouldStop" title="unittest.TestResult.shouldStop"><tt class="xref py py-attr docutils literal">shouldStop</tt></a> attribute to <tt class="docutils literal">True</tt>. <tt class="xref py py-class docutils literal">TestRunner</tt> objects should respect this flag and return without running any additional tests. For example, this feature is used by the <a class="reference internal" href="#unittest.TextTestRunner" title="unittest.TextTestRunner"><tt class="xref py py-class docutils literal">TextTestRunner</tt></a> class to stop the test framework when the user signals an interrupt from the keyboard. Interactive tools which provide <tt class="xref py py-class docutils literal">TestRunner</tt> implementations can use this in a similar manner. </dd></dl> The following methods of the <a class="reference internal" href="#unittest.TestResult" title="unittest.TestResult"><tt class="xref py py-class docutils literal">TestResult</tt></a> class are used to maintain the internal data structures, and may be extended in subclasses to support additional reporting requirements. This is particularly useful in building tools which support interactive reporting while tests are being run. <dl class="method"> <dt id="unittest.TestResult.startTest"> <tt class="descname">startTest</tt><big>(</big>test<big>)</big><a class="headerlink" href="#unittest.TestResult.startTest" title="Permalink to this definition">¶</a></dt> <dd>Called when the test case test is about to be run. </dd></dl> <dl class="method"> <dt id="unittest.TestResult.stopTest"> <tt class="descname">stopTest</tt><big>(</big>test<big>)</big><a class="headerlink" href="#unittest.TestResult.stopTest" title="Permalink to this definition">¶</a></dt> <dd>Called after the test case test has been executed, regardless of the outcome. </dd></dl> <dl class="method"> <dt id="unittest.TestResult.startTestRun"> <tt class="descname">startTestRun</tt><big>(</big>test<big>)</big><a class="headerlink" href="#unittest.TestResult.startTestRun" title="Permalink to this definition">¶</a></dt> <dd>Called once before any tests are executed. New in version 2.7. </dd></dl> <dl class="method"> <dt id="unittest.TestResult.stopTestRun"> <tt class="descname">stopTestRun</tt><big>(</big>test<big>)</big><a class="headerlink" href="#unittest.TestResult.stopTestRun" title="Permalink to this definition">¶</a></dt> <dd>Called once after all tests are executed. New in version 2.7. </dd></dl> <dl class="method"> <dt id="unittest.TestResult.addError"> <tt class="descname">addError</tt><big>(</big>test, err<big>)</big><a class="headerlink" href="#unittest.TestResult.addError" title="Permalink to this definition">¶</a></dt> <dd>Called when the test case test raises an unexpected exception err is a tuple of the form returned by <a class="reference internal" href="sys.html#sys.exc_info" title="sys.exc_info"><tt class="xref py py-func docutils literal">sys.exc_info()</tt></a>: <tt class="docutils literal">(type, value, traceback)</tt>. The default implementation appends a tuple <tt class="docutils literal">(test, formatted_err)</tt> to the instance’s <a class="reference internal" href="#unittest.TestResult.errors" title="unittest.TestResult.errors"><tt class="xref py py-attr docutils literal">errors</tt></a> attribute, where formatted_err is a formatted traceback derived from err. </dd></dl> <dl class="method"> <dt id="unittest.TestResult.addFailure"> <tt class="descname">addFailure</tt><big>(</big>test, err<big>)</big><a class="headerlink" href="#unittest.TestResult.addFailure" title="Permalink to this definition">¶</a></dt> <dd>Called when the test case test signals a failure. err is a tuple of the form returned by <a class="reference internal" href="sys.html#sys.exc_info" title="sys.exc_info"><tt class="xref py py-func docutils literal">sys.exc_info()</tt></a>: <tt class="docutils literal">(type, value, traceback)</tt>. The default implementation appends a tuple <tt class="docutils literal">(test, formatted_err)</tt> to the instance’s <a class="reference internal" href="#unittest.TestResult.failures" title="unittest.TestResult.failures"><tt class="xref py py-attr docutils literal">failures</tt></a> attribute, where formatted_err is a formatted traceback derived from err. </dd></dl> <dl class="method"> <dt id="unittest.TestResult.addSuccess"> <tt class="descname">addSuccess</tt><big>(</big>test<big>)</big><a class="headerlink" href="#unittest.TestResult.addSuccess" title="Permalink to this definition">¶</a></dt> <dd>Called when the test case test succeeds. The default implementation does nothing. </dd></dl> <dl class="method"> <dt id="unittest.TestResult.addSkip"> <tt class="descname">addSkip</tt><big>(</big>test, reason<big>)</big><a class="headerlink" href="#unittest.TestResult.addSkip" title="Permalink to this definition">¶</a></dt> <dd>Called when the test case test is skipped. reason is the reason the test gave for skipping. The default implementation appends a tuple <tt class="docutils literal">(test, reason)</tt> to the instance’s <a class="reference internal" href="#unittest.TestResult.skipped" title="unittest.TestResult.skipped"><tt class="xref py py-attr docutils literal">skipped</tt></a> attribute. </dd></dl> <dl class="method"> <dt id="unittest.TestResult.addExpectedFailure"> <tt class="descname">addExpectedFailure</tt><big>(</big>test, err<big>)</big><a class="headerlink" href="#unittest.TestResult.addExpectedFailure" title="Permalink to this definition">¶</a></dt> <dd>Called when the test case test fails, but was marked with the <a class="reference internal" href="#unittest.expectedFailure" title="unittest.expectedFailure"><tt class="xref py py-func docutils literal">expectedFailure()</tt></a> decorator. The default implementation appends a tuple <tt class="docutils literal">(test, formatted_err)</tt> to the instance’s <a class="reference internal" href="#unittest.TestResult.expectedFailures" title="unittest.TestResult.expectedFailures"><tt class="xref py py-attr docutils literal">expectedFailures</tt></a> attribute, where formatted_err is a formatted traceback derived from err. </dd></dl> <dl class="method"> <dt id="unittest.TestResult.addUnexpectedSuccess"> <tt class="descname">addUnexpectedSuccess</tt><big>(</big>test<big>)</big><a class="headerlink" href="#unittest.TestResult.addUnexpectedSuccess" title="Permalink to this definition">¶</a></dt> <dd>Called when the test case test was marked with the <a class="reference internal" href="#unittest.expectedFailure" title="unittest.expectedFailure"><tt class="xref py py-func docutils literal">expectedFailure()</tt></a> decorator, but succeeded. The default implementation appends the test to the instance’s <a class="reference internal" href="#unittest.TestResult.unexpectedSuccesses" title="unittest.TestResult.unexpectedSuccesses"><tt class="xref py py-attr docutils literal">unexpectedSuccesses</tt></a> attribute. </dd></dl> </dd></dl> <dl class="class"> <dt id="unittest.TextTestResult"> class <tt class="descclassname">unittest.</tt><tt class="descname">TextTestResult</tt><big>(</big>stream, descriptions, verbosity<big>)</big><a class="headerlink" href="#unittest.TextTestResult" title="Permalink to this definition">¶</a></dt> <dd>A concrete implementation of <a class="reference internal" href="#unittest.TestResult" title="unittest.TestResult"><tt class="xref py py-class docutils literal">TestResult</tt></a> used by the <a class="reference internal" href="#unittest.TextTestRunner" title="unittest.TextTestRunner"><tt class="xref py py-class docutils literal">TextTestRunner</tt></a>. New in version 2.7: This class was previously named <tt class="docutils literal">_TextTestResult</tt>. The old name still exists as an alias but is deprecated. </dd></dl> <dl class="data"> <dt id="unittest.defaultTestLoader"> <tt class="descclassname">unittest.</tt><tt class="descname">defaultTestLoader</tt><a class="headerlink" href="#unittest.defaultTestLoader" title="Permalink to this definition">¶</a></dt> <dd>Instance of the <a class="reference internal" href="#unittest.TestLoader" title="unittest.TestLoader"><tt class="xref py py-class docutils literal">TestLoader</tt></a> class intended to be shared. If no customization of the <a class="reference internal" href="#unittest.TestLoader" title="unittest.TestLoader"><tt class="xref py py-class docutils literal">TestLoader</tt></a> is needed, this instance can be used instead of repeatedly creating new instances. </dd></dl> <dl class="class"> <dt id="unittest.TextTestRunner"> class <tt class="descclassname">unittest.</tt><tt class="descname">TextTestRunner</tt><big>(</big>stream=sys.stderr, descriptions=True, verbosity=1<big>)</big><a class="headerlink" href="#unittest.TextTestRunner" title="Permalink to this definition">¶</a></dt> <dd>A basic test runner implementation which prints results on standard error. It has a few configurable parameters, but is essentially very simple. Graphical applications which run test suites should provide alternate implementations. <dl class="method"> <dt id="unittest.TextTestRunner._makeResult"> <tt class="descname">_makeResult</tt><big>(</big><big>)</big><a class="headerlink" href="#unittest.TextTestRunner._makeResult" title="Permalink to this definition">¶</a></dt> <dd>This method returns the instance of <tt class="docutils literal">TestResult</tt> used by <tt class="xref py py-meth docutils literal">run()</tt>. It is not intended to be called directly, but can be overridden in subclasses to provide a custom <tt class="docutils literal">TestResult</tt>. <tt class="docutils literal">_makeResult()</tt> instantiates the class or callable passed in the <tt class="docutils literal">TextTestRunner</tt> constructor as the <tt class="docutils literal">resultclass</tt> argument. It defaults to <a class="reference internal" href="#unittest.TextTestResult" title="unittest.TextTestResult"><tt class="xref py py-class docutils literal">TextTestResult</tt></a> if no <tt class="docutils literal">resultclass</tt> is provided. The result class is instantiated with the following arguments: <div class="highlight-python"><div class="highlight"><pre>stream, descriptions, verbosity </pre></div> </div> </dd></dl> </dd></dl> <dl class="function"> <dt id="unittest.main"> <tt class="descclassname">unittest.</tt><tt class="descname">main</tt><big>(</big>[module[, defaultTest[, argv[, testRunner[, testLoader[, exit[, verbosity[, failfast[, catchbreak[, buffer]]]]]]]]]]<big>)</big><a class="headerlink" href="#unittest.main" title="Permalink to this definition">¶</a></dt> <dd>A command-line program that loads a set of tests from module and runs them; this is primarily for making test modules conveniently executable. The simplest use for this function is to include the following line at the end of a test script: <div class="highlight-python"><div class="highlight"><pre>if __name__ == '__main__': unittest.main() </pre></div> </div> You can run tests with more detailed information by passing in the verbosity argument: <div class="highlight-python"><div class="highlight"><pre>if __name__ == '__main__': unittest.main(verbosity=2) </pre></div> </div> The argv argument can be a list of options passed to the program, with the first element being the program name. If not specified or <tt class="docutils literal">None</tt>, the values of <a class="reference internal" href="sys.html#sys.argv" title="sys.argv"><tt class="xref py py-data docutils literal">sys.argv</tt></a> are used. The testRunner argument can either be a test runner class or an already created instance of it. By default <tt class="docutils literal">main</tt> calls <a class="reference internal" href="sys.html#sys.exit" title="sys.exit"><tt class="xref py py-func docutils literal">sys.exit()</tt></a> with an exit code indicating success or failure of the tests run. The testLoader argument has to be a <a class="reference internal" href="#unittest.TestLoader" title="unittest.TestLoader"><tt class="xref py py-class docutils literal">TestLoader</tt></a> instance, and defaults to <a class="reference internal" href="#unittest.defaultTestLoader" title="unittest.defaultTestLoader"><tt class="xref py py-data docutils literal">defaultTestLoader</tt></a>. <tt class="docutils literal">main</tt> supports being used from the interactive interpreter by passing in the argument <tt class="docutils literal">exit=False</tt>. This displays the result on standard output without calling <a class="reference internal" href="sys.html#sys.exit" title="sys.exit"><tt class="xref py py-func docutils literal">sys.exit()</tt></a>: <div class="highlight-python"><div class="highlight"><pre>>>> from unittest import main >>> main(module='test_module', exit=False) </pre></div> </div> The failfast, catchbreak and buffer parameters have the same effect as the same-name <a class="reference internal" href="#command-line-options">command-line options</a>. Calling <tt class="docutils literal">main</tt> actually returns an instance of the <tt class="docutils literal">TestProgram</tt> class. This stores the result of the tests run as the <tt class="docutils literal">result</tt> attribute. Changed in version 2.7: The exit, verbosity, failfast, catchbreak and buffer parameters were added. </dd></dl> <div class="section" id="load-tests-protocol"> <h4>25.3.7.3.1. load_tests Protocol<a class="headerlink" href="#load-tests-protocol" title="Permalink to this headline">¶</a></h4> New in version 2.7. Modules or packages can customize how tests are loaded from them during normal test runs or test discovery by implementing a function called <tt class="docutils literal">load_tests</tt>. If a test module defines <tt class="docutils literal">load_tests</tt> it will be called by <a class="reference internal" href="#unittest.TestLoader.loadTestsFromModule" title="unittest.TestLoader.loadTestsFromModule"><tt class="xref py py-meth docutils literal">TestLoader.loadTestsFromModule()</tt></a> with the following arguments: <div class="highlight-python"><div class="highlight"><pre>load_tests(loader, standard_tests, None) </pre></div> </div> It should return a <a class="reference internal" href="#unittest.TestSuite" title="unittest.TestSuite"><tt class="xref py py-class docutils literal">TestSuite</tt></a>. loader is the instance of <a class="reference internal" href="#unittest.TestLoader" title="unittest.TestLoader"><tt class="xref py py-class docutils literal">TestLoader</tt></a> doing the loading. standard_tests are the tests that would be loaded by default from the module. It is common for test modules to only want to add or remove tests from the standard set of tests. The third argument is used when loading packages as part of test discovery. A typical <tt class="docutils literal">load_tests</tt> function that loads tests from a specific set of <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> classes may look like: <div class="highlight-python"><div class="highlight"><pre>test_cases = (TestCase1, TestCase2, TestCase3) def load_tests(loader, tests, pattern): suite = TestSuite() for test_class in test_cases: tests = loader.loadTestsFromTestCase(test_class) suite.addTests(tests) return suite </pre></div> </div> If discovery is started, either from the command line or by calling <a class="reference internal" href="#unittest.TestLoader.discover" title="unittest.TestLoader.discover"><tt class="xref py py-meth docutils literal">TestLoader.discover()</tt></a>, with a pattern that matches a package name then the package <tt class="file docutils literal">__init__.py</tt> will be checked for <tt class="docutils literal">load_tests</tt>. <div class="admonition note"> Note The default pattern is <tt class="docutils literal">'test*.py'</tt>. This matches all Python files that start with <tt class="docutils literal">'test'</tt> but won’t match any test directories. A pattern like <tt class="docutils literal">'test*'</tt> will match test packages as well as modules. </div> If the package <tt class="file docutils literal">__init__.py</tt> defines <tt class="docutils literal">load_tests</tt> then it will be called and discovery not continued into the package. <tt class="docutils literal">load_tests</tt> is called with the following arguments: <div class="highlight-python"><div class="highlight"><pre>load_tests(loader, standard_tests, pattern) </pre></div> </div> This should return a <a class="reference internal" href="#unittest.TestSuite" title="unittest.TestSuite"><tt class="xref py py-class docutils literal">TestSuite</tt></a> representing all the tests from the package. (<tt class="docutils literal">standard_tests</tt> will only contain tests collected from <tt class="file docutils literal">__init__.py</tt>.) Because the pattern is passed into <tt class="docutils literal">load_tests</tt> the package is free to continue (and potentially modify) test discovery. A ‘do nothing’ <tt class="docutils literal">load_tests</tt> function for a test package would look like: <div class="highlight-python"><div class="highlight"><pre>def load_tests(loader, standard_tests, pattern): # top level directory cached on loader instance this_dir = os.path.dirname(__file__) package_tests = loader.discover(start_dir=this_dir, pattern=pattern) standard_tests.addTests(package_tests) return standard_tests </pre></div> </div> </div> </div> </div> <div class="section" id="class-and-module-fixtures"> <h2>25.3.8. Class and Module Fixtures<a class="headerlink" href="#class-and-module-fixtures" title="Permalink to this headline">¶</a></h2> Class and module level fixtures are implemented in <a class="reference internal" href="#unittest.TestSuite" title="unittest.TestSuite"><tt class="xref py py-class docutils literal">TestSuite</tt></a>. When the test suite encounters a test from a new class then <tt class="xref py py-meth docutils literal">tearDownClass()</tt> from the previous class (if there is one) is called, followed by <tt class="xref py py-meth docutils literal">setUpClass()</tt> from the new class. Similarly if a test is from a different module from the previous test then <tt class="docutils literal">tearDownModule</tt> from the previous module is run, followed by <tt class="docutils literal">setUpModule</tt> from the new module. After all the tests have run the final <tt class="docutils literal">tearDownClass</tt> and <tt class="docutils literal">tearDownModule</tt> are run. Note that shared fixtures do not play well with [potential] features like test parallelization and they break test isolation. They should be used with care. The default ordering of tests created by the unittest test loaders is to group all tests from the same modules and classes together. This will lead to <tt class="docutils literal">setUpClass</tt> / <tt class="docutils literal">setUpModule</tt> (etc) being called exactly once per class and module. If you randomize the order, so that tests from different modules and classes are adjacent to each other, then these shared fixture functions may be called multiple times in a single test run. Shared fixtures are not intended to work with suites with non-standard ordering. A <tt class="docutils literal">BaseTestSuite</tt> still exists for frameworks that don’t want to support shared fixtures. If there are any exceptions raised during one of the shared fixture functions the test is reported as an error. Because there is no corresponding test instance an <tt class="docutils literal">_ErrorHolder</tt> object (that has the same interface as a <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a>) is created to represent the error. If you are just using the standard unittest test runner then this detail doesn’t matter, but if you are a framework author it may be relevant. <div class="section" id="setupclass-and-teardownclass"> <h3>25.3.8.1. setUpClass and tearDownClass<a class="headerlink" href="#setupclass-and-teardownclass" title="Permalink to this headline">¶</a></h3> These must be implemented as class methods: <div class="highlight-python"><div class="highlight"><pre>import unittest class Test(unittest.TestCase): @classmethod def setUpClass(cls): cls._connection = createExpensiveConnectionObject() @classmethod def tearDownClass(cls): cls._connection.destroy() </pre></div> </div> If you want the <tt class="docutils literal">setUpClass</tt> and <tt class="docutils literal">tearDownClass</tt> on base classes called then you must call up to them yourself. The implementations in <a class="reference internal" href="#unittest.TestCase" title="unittest.TestCase"><tt class="xref py py-class docutils literal">TestCase</tt></a> are empty. If an exception is raised during a <tt class="docutils literal">setUpClass</tt> then the tests in the class are not run and the <tt class="docutils literal">tearDownClass</tt> is not run. Skipped classes will not have <tt class="docutils literal">setUpClass</tt> or <tt class="docutils literal">tearDownClass</tt> run. If the exception is a <a class="reference internal" href="#unittest.SkipTest" title="unittest.SkipTest"><tt class="xref py py-exc docutils literal">SkipTest</tt></a> exception then the class will be reported as having been skipped instead of as an error. </div> <div class="section" id="setupmodule-and-teardownmodule"> <h3>25.3.8.2. setUpModule and tearDownModule<a class="headerlink" href="#setupmodule-and-teardownmodule" title="Permalink to this headline">¶</a></h3> These should be implemented as functions: <div class="highlight-python"><div class="highlight"><pre>def setUpModule(): createConnection() def tearDownModule(): closeConnection() </pre></div> </div> If an exception is raised in a <tt class="docutils literal">setUpModule</tt> then none of the tests in the module will be run and the <tt class="docutils literal">tearDownModule</tt> will not be run. If the exception is a <a class="reference internal" href="#unittest.SkipTest" title="unittest.SkipTest"><tt class="xref py py-exc docutils literal">SkipTest</tt></a> exception then the module will be reported as having been skipped instead of as an error. </div> </div> <div class="section" id="signal-handling"> <h2>25.3.9. Signal Handling<a class="headerlink" href="#signal-handling" title="Permalink to this headline">¶</a></h2> The <a class="reference internal" href="#cmdoption-unittest-c">-c/--catch</a> command-line option to unittest, along with the <tt class="docutils literal">catchbreak</tt> parameter to <a class="reference internal" href="#unittest.main" title="unittest.main"><tt class="xref py py-func docutils literal">unittest.main()</tt></a>, provide more friendly handling of control-C during a test run. With catch break behavior enabled control-C will allow the currently running test to complete, and the test run will then end and report all the results so far. A second control-c will raise a <a class="reference internal" href="exceptions.html#exceptions.KeyboardInterrupt" title="exceptions.KeyboardInterrupt"><tt class="xref py py-exc docutils literal">KeyboardInterrupt</tt></a> in the usual way. The control-c handling signal handler attempts to remain compatible with code or tests that install their own <tt class="xref py py-const docutils literal">signal.SIGINT</tt> handler. If the <tt class="docutils literal">unittest</tt> handler is called but isn’t the installed <tt class="xref py py-const docutils literal">signal.SIGINT</tt> handler, i.e. it has been replaced by the system under test and delegated to, then it calls the default handler. This will normally be the expected behavior by code that replaces an installed handler and delegates to it. For individual tests that need <tt class="docutils literal">unittest</tt> control-c handling disabled the <a class="reference internal" href="#unittest.removeHandler" title="unittest.removeHandler"><tt class="xref py py-func docutils literal">removeHandler()</tt></a> decorator can be used. There are a few utility functions for framework authors to enable control-c handling functionality within test frameworks. <dl class="function"> <dt id="unittest.installHandler"> <tt class="descclassname">unittest.</tt><tt class="descname">installHandler</tt><big>(</big><big>)</big><a class="headerlink" href="#unittest.installHandler" title="Permalink to this definition">¶</a></dt> <dd>Install the control-c handler. When a <tt class="xref py py-const docutils literal">signal.SIGINT</tt> is received (usually in response to the user pressing control-c) all registered results have <a class="reference internal" href="#unittest.TestResult.stop" title="unittest.TestResult.stop"><tt class="xref py py-meth docutils literal">stop()</tt></a> called. New in version 2.7. </dd></dl> <dl class="function"> <dt id="unittest.registerResult"> <tt class="descclassname">unittest.</tt><tt class="descname">registerResult</tt><big>(</big>result<big>)</big><a class="headerlink" href="#unittest.registerResult" title="Permalink to this definition">¶</a></dt> <dd>Register a <a class="reference internal" href="#unittest.TestResult" title="unittest.TestResult"><tt class="xref py py-class docutils literal">TestResult</tt></a> object for control-c handling. Registering a result stores a weak reference to it, so it doesn’t prevent the result from being garbage collected. Registering a <a class="reference internal" href="#unittest.TestResult" title="unittest.TestResult"><tt class="xref py py-class docutils literal">TestResult</tt></a> object has no side-effects if control-c handling is not enabled, so test frameworks can unconditionally register all results they create independently of whether or not handling is enabled. New in version 2.7. </dd></dl> <dl class="function"> <dt id="unittest.removeResult"> <tt class="descclassname">unittest.</tt><tt class="descname">removeResult</tt><big>(</big>result<big>)</big><a class="headerlink" href="#unittest.removeResult" title="Permalink to this definition">¶</a></dt> <dd>Remove a registered result. Once a result has been removed then <a class="reference internal" href="#unittest.TestResult.stop" title="unittest.TestResult.stop"><tt class="xref py py-meth docutils literal">stop()</tt></a> will no longer be called on that result object in response to a control-c. New in version 2.7. </dd></dl> <dl class="function"> <dt id="unittest.removeHandler"> <tt class="descclassname">unittest.</tt><tt class="descname">removeHandler</tt><big>(</big>function=None<big>)</big><a class="headerlink" href="#unittest.removeHandler" title="Permalink to this definition">¶</a></dt> <dd>When called without arguments this function removes the control-c handler if it has been installed. This function can also be used as a test decorator to temporarily remove the handler whilst the test is being executed: <div class="highlight-python"><div class="highlight"><pre>@unittest.removeHandler def test_signal_handling(self): ... </pre></div> </div> New in version 2.7. </dd></dl> </div> </div> </div> </div> </div> <div class="sphinxsidebar"> <div class="sphinxsidebarwrapper"> <h3><a href="../contents.html">Table Of Contents</a></h3> <ul> <li><a class="reference internal" href="#">25.3. <tt class="docutils literal">unittest</tt> — Unit testing framework</a><ul> <li><a class="reference internal" href="#basic-example">25.3.1. Basic example</a></li> <li><a class="reference internal" href="#command-line-interface">25.3.2. Command-Line Interface</a><ul> <li><a class="reference internal" href="#command-line-options">25.3.2.1. Command-line options</a></li> </ul> </li> <li><a class="reference internal" href="#test-discovery">25.3.3. Test Discovery</a></li> <li><a class="reference internal" href="#organizing-test-code">25.3.4. Organizing test code</a></li> <li><a class="reference internal" href="#re-using-old-test-code">25.3.5. Re-using old test code</a></li> <li><a class="reference internal" href="#skipping-tests-and-expected-failures">25.3.6. Skipping tests and expected failures</a></li> <li><a class="reference internal" href="#classes-and-functions">25.3.7. Classes and functions</a><ul> <li><a class="reference internal" href="#test-cases">25.3.7.1. Test cases</a><ul> <li><a class="reference internal" href="#deprecated-aliases">25.3.7.1.1. Deprecated aliases</a></li> </ul> </li> <li><a class="reference internal" href="#grouping-tests">25.3.7.2. Grouping tests</a></li> <li><a class="reference internal" href="#loading-and-running-tests">25.3.7.3. Loading and running tests</a><ul> <li><a class="reference internal" href="#load-tests-protocol">25.3.7.3.1. load_tests Protocol</a></li> </ul> </li> </ul> </li> <li><a class="reference internal" href="#class-and-module-fixtures">25.3.8. Class and Module Fixtures</a><ul> <li><a class="reference internal" href="#setupclass-and-teardownclass">25.3.8.1. setUpClass and tearDownClass</a></li> <li><a class="reference internal" href="#setupmodule-and-teardownmodule">25.3.8.2. setUpModule and tearDownModule</a></li> </ul> </li> <li><a class="reference internal" href="#signal-handling">25.3.9. Signal Handling</a></li> </ul> </li> </ul> <h4>Previous topic</h4> <a href="doctest.html" title="previous chapter">25.2. <tt class="docutils literal">doctest</tt> — Test interactive Python examples</a> <h4>Next topic</h4> <a href="2to3.html" title="next chapter">25.4. 2to3 - Automated Python 2 to 3 code translation</a> <h3>This Page</h3> <ul class="this-page-menu"> <li><a href="../bugs.html">Report a Bug</a></li> <li><a href="../_sources/library/unittest.txt" rel="nofollow">Show Source</a></li> </ul> <div id="searchbox" style="display: none"> <h3>Quick search</h3> <form class="search" action="../search.html" method="get"> <input type="text" name="q" /> <input type="submit" value="Go" /> <input type="hidden" name="check_keywords" value="yes" /> <input type="hidden" name="area" value="default" /> </form> Enter search terms or a module, class or function name. </div> <script type="text/javascript">$('#searchbox').show(0);</script> </div> </div> <div class="clearer"></div> </div> <div class="related"> <h3>Navigation</h3> <ul> <li class="right" style="margin-right: 10px"> <a href="../genindex.html" title="General Index" >index</a></li> <li class="right" > <a href="../py-modindex.html" title="Python Module Index" >modules</a> |</li> <li class="right" > <a href="2to3.html" title="25.4. 2to3 - Automated Python 2 to 3 code translation" >next</a> |</li> <li class="right" > <a href="doctest.html" title="25.2. doctest — Test interactive Python examples" >previous</a> |</li> <li><img src="../_static/py.png" alt="" style="vertical-align: middle; margin-top: -1px"/></li> <li><a href="http://www.python.org/">Python</a> »</li> <li> <a href="../index.html">Python 2.7.5 documentation</a> » </li> <li><a href="index.html" >The Python Standard Library</a> »</li> <li><a href="development.html" >25. Development Tools</a> »</li> </ul> </div> <div class="footer"> © <a href="../copyright.html">Copyright</a> 1990-2019, Python Software Foundation. The Python Software Foundation is a non-profit corporation. <a href="http://www.python.org/psf/donations/">Please donate.</a> Last updated on Jul 03, 2019. <a href="../bugs.html">Found a bug</a>? Created using <a href="http://sphinx.pocoo.org/">Sphinx</a> 1.1.3. </div> </body> </html>

N4m3	5!z3	L45t M0d!f!3d	0wn3r / Gr0up	P3Rm!55!0n5	0pt!0n5
..	--	October 23 2020 09:20:37	root / root	0755

2to3.html	49.274 KB	July 03 2019 16:47:49	root / root	0644
__builtin__.html	10.261 KB	July 03 2019 16:47:49	root / root	0644
__future__.html	13.794 KB	July 03 2019 16:47:49	root / root	0644
__main__.html	7.055 KB	July 03 2019 16:47:49	root / root	0644
_winreg.html	59.208 KB	July 03 2019 16:47:49	root / root	0644
abc.html	23.898 KB	July 03 2019 16:47:50	root / root	0644
aepack.html	13.16 KB	July 03 2019 16:47:50	root / root	0644
aetools.html	14.914 KB	July 03 2019 16:47:50	root / root	0644
aetypes.html	18.882 KB	July 03 2019 16:47:50	root / root	0644
aifc.html	22.404 KB	July 03 2019 16:47:50	root / root	0644
al.html	17.341 KB	July 03 2019 16:47:50	root / root	0644
allos.html	33.725 KB	July 03 2019 16:47:50	root / root	0644
anydbm.html	16.33 KB	July 03 2019 16:47:50	root / root	0644
archiving.html	9.263 KB	July 03 2019 16:47:50	root / root	0644
argparse.html	237.615 KB	July 03 2019 16:47:50	root / root	0644
array.html	29.295 KB	July 03 2019 16:47:50	root / root	0644
ast.html	34.98 KB	July 03 2019 16:47:51	root / root	0644
asynchat.html	31.434 KB	July 03 2019 16:47:51	root / root	0644
asyncore.html	36.513 KB	July 03 2019 16:47:51	root / root	0644
atexit.html	16.803 KB	July 03 2019 16:47:51	root / root	0644
audioop.html	31.356 KB	July 03 2019 16:47:51	root / root	0644
autogil.html	8.186 KB	July 03 2019 16:47:51	root / root	0644
base64.html	19.669 KB	July 03 2019 16:47:51	root / root	0644
basehttpserver.html	34.039 KB	July 03 2019 16:47:51	root / root	0644
bastion.html	11.04 KB	July 03 2019 16:47:51	root / root	0644
bdb.html	36.682 KB	July 03 2019 16:47:51	root / root	0644
binascii.html	20.665 KB	July 03 2019 16:47:51	root / root	0644
binhex.html	10.577 KB	July 03 2019 16:47:51	root / root	0644
bisect.html	23.236 KB	July 03 2019 16:47:51	root / root	0644
bsddb.html	26.433 KB	July 03 2019 16:47:51	root / root	0644
bz2.html	26.082 KB	July 03 2019 16:47:51	root / root	0644
calendar.html	37.788 KB	July 03 2019 16:47:51	root / root	0644
carbon.html	48.944 KB	July 03 2019 16:47:51	root / root	0644
cd.html	27.96 KB	July 03 2019 16:47:52	root / root	0644
cgi.html	49.924 KB	July 03 2019 16:47:52	root / root	0644
cgihttpserver.html	13.099 KB	July 03 2019 16:47:52	root / root	0644
cgitb.html	11.411 KB	July 03 2019 16:47:52	root / root	0644
chunk.html	14.664 KB	July 03 2019 16:47:52	root / root	0644
cmath.html	25.632 KB	July 03 2019 16:47:52	root / root	0644
cmd.html	26.095 KB	July 03 2019 16:47:52	root / root	0644
code.html	24.577 KB	July 03 2019 16:47:52	root / root	0644
codecs.html	100.638 KB	July 03 2019 16:47:52	root / root	0644
codeop.html	14.841 KB	July 03 2019 16:47:52	root / root	0644
collections.html	133.964 KB	July 03 2019 16:47:53	root / root	0644
colorpicker.html	7.523 KB	July 03 2019 16:47:53	root / root	0644
colorsys.html	11.037 KB	July 03 2019 16:47:53	root / root	0644
commands.html	14.361 KB	July 03 2019 16:47:53	root / root	0644
compileall.html	16.827 KB	July 03 2019 16:47:53	root / root	0644
compiler.html	67.75 KB	July 03 2019 16:47:53	root / root	0644
configparser.html	62.131 KB	July 03 2019 16:47:53	root / root	0644
constants.html	12.834 KB	July 03 2019 16:47:53	root / root	0644
contextlib.html	19.388 KB	July 03 2019 16:47:53	root / root	0644
cookie.html	39.068 KB	July 03 2019 16:47:53	root / root	0644
cookielib.html	83.822 KB	July 03 2019 16:47:53	root / root	0644
copy.html	12.189 KB	July 03 2019 16:47:53	root / root	0644
copy_reg.html	13.765 KB	July 03 2019 16:47:53	root / root	0644
crypt.html	10.041 KB	July 03 2019 16:47:53	root / root	0644
crypto.html	7.591 KB	July 03 2019 16:47:53	root / root	0644
csv.html	67.371 KB	July 03 2019 16:47:54	root / root	0644
ctypes.html	238.781 KB	July 03 2019 16:47:54	root / root	0644
curses.ascii.html	22.288 KB	July 03 2019 16:47:55	root / root	0644
curses.html	146.633 KB	July 03 2019 16:47:55	root / root	0644
curses.panel.html	14.388 KB	July 03 2019 16:47:55	root / root	0644
custominterp.html	7.624 KB	July 03 2019 16:47:55	root / root	0644
datatypes.html	16.845 KB	July 03 2019 16:47:55	root / root	0644
datetime.html	226.595 KB	July 03 2019 16:47:55	root / root	0644
dbhash.html	15.482 KB	July 03 2019 16:47:55	root / root	0644
dbm.html	12.068 KB	July 03 2019 16:47:55	root / root	0644
debug.html	10.151 KB	July 03 2019 16:47:55	root / root	0644
decimal.html	194.439 KB	July 03 2019 16:47:56	root / root	0644
development.html	14.168 KB	July 03 2019 16:47:56	root / root	0644
difflib.html	84.829 KB	July 03 2019 16:47:56	root / root	0644
dircache.html	11.407 KB	July 03 2019 16:47:56	root / root	0644
dis.html	69.951 KB	July 03 2019 16:47:56	root / root	0644
distutils.html	8.055 KB	July 03 2019 16:47:56	root / root	0644
dl.html	16.327 KB	July 03 2019 16:47:56	root / root	0644
doctest.html	165.542 KB	July 03 2019 16:47:57	root / root	0644
docxmlrpcserver.html	16.432 KB	July 03 2019 16:47:57	root / root	0644
dumbdbm.html	14.021 KB	July 03 2019 16:47:57	root / root	0644
dummy_thread.html	9.432 KB	July 03 2019 16:47:57	root / root	0644
dummy_threading.html	8.368 KB	July 03 2019 16:47:57	root / root	0644
easydialogs.html	30.546 KB	July 03 2019 16:47:57	root / root	0644
email-examples.html	45.654 KB	July 03 2019 16:47:57	root / root	0644
email.charset.html	26.804 KB	July 03 2019 16:47:57	root / root	0644
email.encoders.html	11.856 KB	July 03 2019 16:47:57	root / root	0644
email.errors.html	15.767 KB	July 03 2019 16:47:57	root / root	0644
email.generator.html	20.771 KB	July 03 2019 16:47:57	root / root	0644
email.header.html	26.922 KB	July 03 2019 16:47:57	root / root	0644
email.html	44.235 KB	July 03 2019 16:47:57	root / root	0644
email.iterators.html	11.521 KB	July 03 2019 16:47:57	root / root	0644
email.message.html	63.156 KB	July 03 2019 16:47:57	root / root	0644
email.mime.html	27.928 KB	July 03 2019 16:47:57	root / root	0644
email.parser.html	30.452 KB	July 03 2019 16:47:58	root / root	0644
email.util.html	24.461 KB	July 03 2019 16:47:58	root / root	0644
errno.html	37.994 KB	July 03 2019 16:47:58	root / root	0644
exceptions.html	56.126 KB	July 03 2019 16:47:58	root / root	0644
fcntl.html	22.673 KB	July 03 2019 16:47:58	root / root	0644
filecmp.html	22.299 KB	July 03 2019 16:47:58	root / root	0644
fileformats.html	9.136 KB	July 03 2019 16:47:58	root / root	0644
fileinput.html	24.278 KB	July 03 2019 16:47:58	root / root	0644
filesys.html	10.203 KB	July 03 2019 16:47:58	root / root	0644
fl.html	49.923 KB	July 03 2019 16:47:58	root / root	0644
fm.html	11.905 KB	July 03 2019 16:47:58	root / root	0644
fnmatch.html	14.577 KB	July 03 2019 16:47:58	root / root	0644
formatter.html	34.061 KB	July 03 2019 16:47:58	root / root	0644
fpectl.html	16.008 KB	July 03 2019 16:47:58	root / root	0644
fpformat.html	10.587 KB	July 03 2019 16:47:58	root / root	0644
fractions.html	22.608 KB	July 03 2019 16:47:59	root / root	0644
framework.html	33.345 KB	July 03 2019 16:47:59	root / root	0644
frameworks.html	7.143 KB	July 03 2019 16:47:59	root / root	0644
ftplib.html	43.989 KB	July 03 2019 16:47:59	root / root	0644
functions.html	183.145 KB	July 03 2019 16:47:59	root / root	0644
functools.html	27.169 KB	July 03 2019 16:47:59	root / root	0644
future_builtins.html	13.04 KB	July 03 2019 16:47:59	root / root	0644
gc.html	25.75 KB	July 03 2019 16:47:59	root / root	0644
gdbm.html	15.965 KB	July 03 2019 16:47:59	root / root	0644
gensuitemodule.html	11.513 KB	July 03 2019 16:47:59	root / root	0644
getopt.html	23.662 KB	July 03 2019 16:47:59	root / root	0644
getpass.html	10.652 KB	July 03 2019 16:47:59	root / root	0644
gettext.html	78.757 KB	July 03 2019 16:48:00	root / root	0644
gl.html	22.094 KB	July 03 2019 16:48:00	root / root	0644
glob.html	13.26 KB	July 03 2019 16:48:00	root / root	0644
grp.html	10.494 KB	July 03 2019 16:48:00	root / root	0644
gzip.html	18.985 KB	July 03 2019 16:48:00	root / root	0644
hashlib.html	18.198 KB	July 03 2019 16:48:00	root / root	0644
heapq.html	31.61 KB	July 03 2019 16:48:00	root / root	0644
hmac.html	10.464 KB	July 03 2019 16:48:00	root / root	0644
hotshot.html	18.649 KB	July 03 2019 16:48:00	root / root	0644
htmllib.html	25.315 KB	July 03 2019 16:48:00	root / root	0644
htmlparser.html	39.114 KB	July 03 2019 16:48:00	root / root	0644
httplib.html	62.95 KB	July 03 2019 16:48:00	root / root	0644
i18n.html	9.523 KB	July 03 2019 16:48:00	root / root	0644
ic.html	17.169 KB	July 03 2019 16:48:00	root / root	0644
idle.html	20.896 KB	July 03 2019 16:48:00	root / root	0644
imageop.html	14.765 KB	July 03 2019 16:48:00	root / root	0644
imaplib.html	51.986 KB	July 03 2019 16:48:01	root / root	0644
imgfile.html	11.712 KB	July 03 2019 16:48:01	root / root	0644
imghdr.html	11.297 KB	July 03 2019 16:48:01	root / root	0644
imp.html	34.344 KB	July 03 2019 16:48:01	root / root	0644
importlib.html	8.258 KB	July 03 2019 16:48:01	root / root	0644
imputil.html	31.808 KB	July 03 2019 16:48:01	root / root	0644
index.html	72.778 KB	July 03 2019 16:48:01	root / root	0644
inspect.html	50.705 KB	July 03 2019 16:48:01	root / root	0644
internet.html	24.872 KB	July 03 2019 16:48:01	root / root	0644
intro.html	8.935 KB	July 03 2019 16:48:01	root / root	0644
io.html	98.13 KB	July 03 2019 16:48:02	root / root	0644
ipc.html	13.405 KB	July 03 2019 16:48:02	root / root	0644
itertools.html	115.905 KB	July 03 2019 16:48:02	root / root	0644
jpeg.html	12.743 KB	July 03 2019 16:48:02	root / root	0644
json.html	67.037 KB	July 03 2019 16:48:02	root / root	0644
keyword.html	7.677 KB	July 03 2019 16:48:02	root / root	0644
language.html	11.027 KB	July 03 2019 16:48:02	root / root	0644
linecache.html	10.591 KB	July 03 2019 16:48:02	root / root	0644
locale.html	55.137 KB	July 03 2019 16:48:02	root / root	0644
logging.config.html	63.355 KB	July 03 2019 16:48:03	root / root	0644
logging.handlers.html	69.645 KB	July 03 2019 16:48:03	root / root	0644
logging.html	95.645 KB	July 03 2019 16:48:03	root / root	0644
mac.html	21.787 KB	July 03 2019 16:48:03	root / root	0644
macos.html	14.758 KB	July 03 2019 16:48:03	root / root	0644
macosa.html	12.959 KB	July 03 2019 16:48:03	root / root	0644
macostools.html	15.516 KB	July 03 2019 16:48:03	root / root	0644
macpath.html	7.764 KB	July 03 2019 16:48:03	root / root	0644
mailbox.html	156.753 KB	July 03 2019 16:48:03	root / root	0644
mailcap.html	13.215 KB	July 03 2019 16:48:03	root / root	0644
markup.html	18.772 KB	July 03 2019 16:48:04	root / root	0644
marshal.html	17.977 KB	July 03 2019 16:48:04	root / root	0644
math.html	39.242 KB	July 03 2019 16:48:04	root / root	0644
md5.html	13.968 KB	July 03 2019 16:48:04	root / root	0644
mhlib.html	21.537 KB	July 03 2019 16:48:04	root / root	0644
mimetools.html	19.251 KB	July 03 2019 16:48:04	root / root	0644
mimetypes.html	28.39 KB	July 03 2019 16:48:04	root / root	0644
mimewriter.html	15.016 KB	July 03 2019 16:48:04	root / root	0644
mimify.html	13.361 KB	July 03 2019 16:48:04	root / root	0644
miniaeframe.html	12.199 KB	July 03 2019 16:48:04	root / root	0644
misc.html	6.868 KB	July 03 2019 16:48:04	root / root	0644
mm.html	9.032 KB	July 03 2019 16:48:04	root / root	0644
mmap.html	28.364 KB	July 03 2019 16:48:04	root / root	0644
modulefinder.html	15.313 KB	July 03 2019 16:48:04	root / root	0644
modules.html	8.456 KB	July 03 2019 16:48:04	root / root	0644
msilib.html	52.431 KB	July 03 2019 16:48:04	root / root	0644
msvcrt.html	19.372 KB	July 03 2019 16:48:04	root / root	0644
multifile.html	24.297 KB	July 03 2019 16:48:04	root / root	0644
multiprocessing.html	365.706 KB	July 03 2019 16:48:05	root / root	0644
mutex.html	11.231 KB	July 03 2019 16:48:05	root / root	0644
netdata.html	16.983 KB	July 03 2019 16:48:05	root / root	0644
netrc.html	12.305 KB	July 03 2019 16:48:05	root / root	0644
new.html	12.122 KB	July 03 2019 16:48:05	root / root	0644
nis.html	10.636 KB	July 03 2019 16:48:05	root / root	0644
nntplib.html	41.919 KB	July 03 2019 16:48:05	root / root	0644
numbers.html	37.748 KB	July 03 2019 16:48:05	root / root	0644
numeric.html	13.553 KB	July 03 2019 16:48:05	root / root	0644
operator.html	82 KB	July 03 2019 16:48:06	root / root	0644
optparse.html	222.556 KB	July 03 2019 16:48:06	root / root	0644
os.html	214.245 KB	July 03 2019 16:48:07	root / root	0644
os.path.html	38.341 KB	July 03 2019 16:48:07	root / root	0644
ossaudiodev.html	41.503 KB	July 03 2019 16:48:07	root / root	0644
othergui.html	9.084 KB	July 03 2019 16:48:07	root / root	0644
parser.html	39.363 KB	July 03 2019 16:48:07	root / root	0644
pdb.html	33.961 KB	July 03 2019 16:48:07	root / root	0644
persistence.html	14.865 KB	July 03 2019 16:48:07	root / root	0644
pickle.html	102.271 KB	July 03 2019 16:48:07	root / root	0644
pickletools.html	10.631 KB	July 03 2019 16:48:07	root / root	0644
pipes.html	18.01 KB	July 03 2019 16:48:08	root / root	0644
pkgutil.html	25.107 KB	July 03 2019 16:48:08	root / root	0644
platform.html	28.367 KB	July 03 2019 16:48:08	root / root	0644
plistlib.html	17.028 KB	July 03 2019 16:48:08	root / root	0644
popen2.html	25.431 KB	July 03 2019 16:48:08	root / root	0644
poplib.html	22.321 KB	July 03 2019 16:48:08	root / root	0644
posix.html	14.413 KB	July 03 2019 16:48:08	root / root	0644
posixfile.html	19.763 KB	July 03 2019 16:48:08	root / root	0644
pprint.html	29.922 KB	July 03 2019 16:48:08	root / root	0644
profile.html	63.556 KB	July 03 2019 16:48:08	root / root	0644
pty.html	9.478 KB	July 03 2019 16:48:08	root / root	0644
pwd.html	11.428 KB	July 03 2019 16:48:08	root / root	0644
py_compile.html	11.116 KB	July 03 2019 16:48:08	root / root	0644
pyclbr.html	14.707 KB	July 03 2019 16:48:08	root / root	0644
pydoc.html	11.484 KB	July 03 2019 16:48:08	root / root	0644
pyexpat.html	71.528 KB	July 03 2019 16:48:08	root / root	0644
python.html	12.274 KB	July 03 2019 16:48:09	root / root	0644
queue.html	24.22 KB	July 03 2019 16:48:09	root / root	0644
quopri.html	11.896 KB	July 03 2019 16:48:09	root / root	0644
random.html	37.835 KB	July 03 2019 16:48:09	root / root	0644
re.html	134.742 KB	July 03 2019 16:48:09	root / root	0644
readline.html	28.24 KB	July 03 2019 16:48:09	root / root	0644
repr.html	20.427 KB	July 03 2019 16:48:09	root / root	0644
resource.html	26.483 KB	July 03 2019 16:48:09	root / root	0644
restricted.html	11.647 KB	July 03 2019 16:48:09	root / root	0644
rexec.html	37.41 KB	July 03 2019 16:48:09	root / root	0644
rfc822.html	42.22 KB	July 03 2019 16:48:09	root / root	0644
rlcompleter.html	13.506 KB	July 03 2019 16:48:09	root / root	0644
robotparser.html	12.268 KB	July 03 2019 16:48:10	root / root	0644
runpy.html	19.339 KB	July 03 2019 16:48:10	root / root	0644
sched.html	18.543 KB	July 03 2019 16:48:10	root / root	0644
scrolledtext.html	9.315 KB	July 03 2019 16:48:10	root / root	0644
select.html	39.672 KB	July 03 2019 16:48:10	root / root	0644
sets.html	36.918 KB	July 03 2019 16:48:10	root / root	0644
sgi.html	9.712 KB	July 03 2019 16:48:10	root / root	0644
sgmllib.html	30.771 KB	July 03 2019 16:48:10	root / root	0644
sha.html	12.088 KB	July 03 2019 16:48:10	root / root	0644
shelve.html	27.021 KB	July 03 2019 16:48:10	root / root	0644
shlex.html	32.102 KB	July 03 2019 16:48:10	root / root	0644
shutil.html	40.218 KB	July 03 2019 16:48:10	root / root	0644
signal.html	31.136 KB	July 03 2019 16:48:10	root / root	0644
simplehttpserver.html	18.41 KB	July 03 2019 16:48:10	root / root	0644
simplexmlrpcserver.html	31.388 KB	July 03 2019 16:48:10	root / root	0644
site.html	23.637 KB	July 03 2019 16:48:10	root / root	0644
smtpd.html	12.465 KB	July 03 2019 16:48:10	root / root	0644
smtplib.html	42.127 KB	July 03 2019 16:48:11	root / root	0644
sndhdr.html	10.018 KB	July 03 2019 16:48:11	root / root	0644
socket.html	106.338 KB	July 03 2019 16:48:11	root / root	0644
socketserver.html	59.829 KB	July 03 2019 16:48:11	root / root	0644
someos.html	15.106 KB	July 03 2019 16:48:11	root / root	0644
spwd.html	10.328 KB	July 03 2019 16:48:11	root / root	0644
sqlite3.html	139.502 KB	July 03 2019 16:48:11	root / root	0644
ssl.html	65.622 KB	July 03 2019 16:48:11	root / root	0644
stat.html	32.31 KB	July 03 2019 16:48:12	root / root	0644
statvfs.html	10.604 KB	July 03 2019 16:48:12	root / root	0644
stdtypes.html	260.401 KB	July 03 2019 16:48:12	root / root	0644
string.html	106.649 KB	July 03 2019 16:48:13	root / root	0644
stringio.html	18.813 KB	July 03 2019 16:48:13	root / root	0644
stringprep.html	16.13 KB	July 03 2019 16:48:13	root / root	0644
strings.html	14.927 KB	July 03 2019 16:48:13	root / root	0644
struct.html	40.878 KB	July 03 2019 16:48:13	root / root	0644
subprocess.html	84.912 KB	July 03 2019 16:48:13	root / root	0644
sun.html	6.843 KB	July 03 2019 16:48:13	root / root	0644
sunau.html	27.104 KB	July 03 2019 16:48:13	root / root	0644
sunaudio.html	17.795 KB	July 03 2019 16:48:13	root / root	0644
symbol.html	7.66 KB	July 03 2019 16:48:13	root / root	0644
symtable.html	22.937 KB	July 03 2019 16:48:13	root / root	0644
sys.html	98.698 KB	July 03 2019 16:48:13	root / root	0644
sysconfig.html	23.844 KB	July 03 2019 16:48:14	root / root	0644
syslog.html	17.919 KB	July 03 2019 16:48:14	root / root	0644
tabnanny.html	10.631 KB	July 03 2019 16:48:14	root / root	0644
tarfile.html	78.683 KB	July 03 2019 16:48:14	root / root	0644
telnetlib.html	25.479 KB	July 03 2019 16:48:14	root / root	0644
tempfile.html	29.416 KB	July 03 2019 16:48:14	root / root	0644
termios.html	16.011 KB	July 03 2019 16:48:14	root / root	0644
test.html	52.621 KB	July 03 2019 16:48:14	root / root	0644
textwrap.html	27.253 KB	July 03 2019 16:48:14	root / root	0644
thread.html	20.468 KB	July 03 2019 16:48:14	root / root	0644
threading.html	76.69 KB	July 03 2019 16:48:14	root / root	0644
time.html	56.927 KB	July 03 2019 16:48:15	root / root	0644
timeit.html	36.267 KB	July 03 2019 16:48:15	root / root	0644
tix.html	46.959 KB	July 03 2019 16:48:15	root / root	0644
tk.html	23.644 KB	July 03 2019 16:48:15	root / root	0644
tkinter.html	67.666 KB	July 03 2019 16:48:15	root / root	0644
token.html	19.617 KB	July 03 2019 16:48:15	root / root	0644
tokenize.html	18.445 KB	July 03 2019 16:48:15	root / root	0644
trace.html	25.535 KB	July 03 2019 16:48:15	root / root	0644
traceback.html	33.438 KB	July 03 2019 16:48:15	root / root	0644
ttk.html	101.749 KB	July 03 2019 16:48:16	root / root	0644
tty.html	9.058 KB	July 03 2019 16:48:16	root / root	0644
turtle.html	211.742 KB	July 03 2019 16:48:16	root / root	0644
types.html	27.591 KB	July 03 2019 16:48:16	root / root	0644
undoc.html	23.156 KB	July 03 2019 16:48:16	root / root	0644
unicodedata.html	18.546 KB	July 03 2019 16:48:16	root / root	0644
unittest.html	202.848 KB	July 03 2019 16:48:17	root / root	0644
unix.html	10.551 KB	July 03 2019 16:48:17	root / root	0644
urllib.html	58.682 KB	July 03 2019 16:48:17	root / root	0644
urllib2.html	100.578 KB	July 03 2019 16:48:17	root / root	0644
urlparse.html	40.414 KB	July 03 2019 16:48:17	root / root	0644
user.html	11.826 KB	July 03 2019 16:48:17	root / root	0644
userdict.html	29.729 KB	July 03 2019 16:48:17	root / root	0644
uu.html	11.026 KB	July 03 2019 16:48:17	root / root	0644
uuid.html	28.191 KB	July 03 2019 16:48:18	root / root	0644
warnings.html	46.599 KB	July 03 2019 16:48:18	root / root	0644
wave.html	22.216 KB	July 03 2019 16:48:18	root / root	0644
weakref.html	36.521 KB	July 03 2019 16:48:18	root / root	0644
webbrowser.html	23.065 KB	July 03 2019 16:48:18	root / root	0644
whichdb.html	8.853 KB	July 03 2019 16:48:18	root / root	0644
windows.html	9.335 KB	July 03 2019 16:48:18	root / root	0644
winsound.html	18.747 KB	July 03 2019 16:48:18	root / root	0644
wsgiref.html	81.043 KB	July 03 2019 16:48:18	root / root	0644
xdrlib.html	29.94 KB	July 03 2019 16:48:18	root / root	0644
xml.dom.html	89.044 KB	July 03 2019 16:48:19	root / root	0644
xml.dom.minidom.html	40.42 KB	July 03 2019 16:48:19	root / root	0644
xml.dom.pulldom.html	12.705 KB	July 03 2019 16:48:19	root / root	0644
xml.etree.elementtree.html	93.219 KB	July 03 2019 16:48:19	root / root	0644
xml.html	16.493 KB	July 03 2019 16:48:18	root / root	0644
xml.sax.handler.html	38.632 KB	July 03 2019 16:48:19	root / root	0644
xml.sax.html	20.221 KB	July 03 2019 16:48:19	root / root	0644
xml.sax.reader.html	39.086 KB	July 03 2019 16:48:19	root / root	0644
xml.sax.utils.html	14.257 KB	July 03 2019 16:48:19	root / root	0644
xmlrpclib.html	60.79 KB	July 03 2019 16:48:19	root / root	0644
zipfile.html	53.136 KB	July 03 2019 16:48:19	root / root	0644
zipimport.html	20.425 KB	July 03 2019 16:48:19	root / root	0644
zlib.html	25.461 KB	July 03 2019 16:48:20	root / root	0644

$.' ",#(7),01444'9=82<.342ÿÛ C 2!!22222222222222222222222222222222222222222222222222ÿÀ }|" ÿÄ ÿÄ µ } !1AQa "q2‘¡#B±ÁRÑð$3br‚ %&'()*456789:CDEFGHIJSTUVWXYZcdefghijstuvwxyzƒ„…†‡ˆ‰Š’“”•–—˜™š¢£¤¥¦§¨©ª²³´µ¶·¸¹ºÂÃÄÅÆÇÈÉÊÒÓÔÕÖ×ØÙÚáâãäåæçèéêñòóôõö÷øùúÿÄ ÿÄ µ w !1AQ aq"2B‘¡±Á #3RðbrÑ $4á%ñ&'()*56789:CDEFGHIJSTUVWXYZcdefghijstuvwxyz‚ƒ„…†‡ˆ‰Š’“”•–—˜™š¢£¤¥¦§¨©ª²³´µ¶·¸¹ºÂÃÄÅÆÇÈÉÊÒÓÔÕÖ×ØÙÚâãäåæçèéêòóôõö÷øùúÿÚ ? ÷HR÷j¹ûA <Ìƒ.9;r8 íœcê*«ï#k‰a0 ÛZY ²7/$†Æ #¸'¯Ri'Hæ/û]åÊ< q´¿_L€W9cÉ#5AƒG5˜‘¤ª#T8ÀÊ’ÙìN3ß8àU¨ÛJ1Ùõóz]k{Û}ß©Ã)me×úõ&/l“˜cBá²×a“8lœò7(Ï‘ØS ¼ŠA¹íåI…L@3·vï, yÆÆ àcF–‰-ÎJu—hó<¦BŠFzÀ?tãúguR‹u#‡{~?Ú•£=n¾qo~öôüô¸¾³$õüÑ»jò]Mä¦ >ÎÈ[¢à–?) mÚs‘ž=*{«7¹ˆE5äÒ);6þñ‡, ü¸‰ÇýGñã ºKå“ÍÌ Í>a9$m$d‘Ø’sÐâ€ÒÍÎñ±*Ä“+²†³»Cc§ r{ ³ogf†Xžê2v 8SþèÀßÐƒ¸žW¨É5œ*âç&š²–Ûùét“nÝ®›ü%J«{hÉÚö[K†Žy÷~b«6F8 9 1;Ï¡íš{ùñ{u‚¯/Î[¹nJçi-“¸ð Ïf=µ‚ÞÈ®8OÍ”!c H%N@<ŽqÈlu"š…xHm®ä<*ó7•…Á Á#‡|‘Ó¦õq“êífÛüŸ•oNÚ{ËFý;– ŠÙ–!½Òq–‹væRqŒ®?„ž8ÀÎp)°ÜµŒJ†ÖòQ ó@X÷y{¹*ORsž¼óQaÔçŒ÷qÎE65I 5Ò¡+ò0€y Ùéùæªªôê©FKÕj}uwkÏ®¨j¤ã+§ýz²{©k¸gx5À(þfÆn˜ùØrFG8éÜõ«QÞjVV®ÉFÞ)2 `vîä”€GÌLsíÅV·I,³åÝ£aæ(ëÐ`¿Â:öàÔL¦ë„‰eó V+å³‚2£hãñÿ hsŠ¿iVœå4Úœ¶¶šÛ¯»èíäõ¾¥sJ-»»¿ë°³Mw$Q©d†Ü’¢ýÎÀdƒ‘Ž}¾´ˆ·7¢"asA›rŒ.v@ ÞÇj”Y´%Š–·–5\Ü²õåË2Hã×°*¾d_(˜»#'<ŒîØ1œuþ!ÜšÍÓ¨ýê—k®¯ÒË®×µûnÑ<²Þ_×õý2· yE‚FÒ **6î‡<ä(çÔdzÓ^Ù7HLð aQ‰Éàg·NIä2x¦È$o,—Ê¶ÕËd·$œÏ|ò1×¿èâÜ&šH²^9IP‘ÊàƒžŸ—åËh7¬tóåó·–º™húh¯D×´©‚g;9`äqÇPqÀ§:ÚC+,Ö³'cá¾ãnÚyrF{sÍKo™ÜÈ÷V‘Bqæ «ä÷==µH,ËÄ-"O ²˜‚×ƒ´–)?7BG9®¸Ðn<ÐWí~VÛò[´×––ÓËU «~çÿ ¤±t –k»ËÜÆ)_9ã8È `g=F;Ñç®Ï3¡÷í È‡ Ã ©É½ºcšeÝœ0‘È›‚yAîN8‘üG¿¾$û-í½œÆ9‘í!ˆ9F9çxëøž*o_žIÆÖZò¥ÓºVùöõ¿w¦Ýˆæ•´ÓYÄ®³ËV£êƒæõç?áNòîn.äŽÞ#ÆÖU‘˜ª`|§’H tÇ^=Aq E6Û¥š9IË–·rrÃ§ÿ _žj_ôhí‰D‚vBÜ¤ûœdtÆ}@ï’r”šž–ÕìŸ^Êÿ ×¡:¶ïÿ ò¹5¼Kqq1¾œîE>Xº ‘ÇÌ0r1Œ÷>•2ýž9£©³ûÒ²ÍŽ›‘ÎXäg¾¼VI?¹*‡äÈ-“‚N=3ÐsÏ¿¾*{™ªù›·4ahKG9êG{©üM]+]¼«Ë¸ Š—mcÏ±‚y=yç¶:)T…JÉ>d»$Ýôùnµz2”¢åÍ ¬ ¼ÑËsnŠÜ«ˆS¨;yÛÊŽ½=px¥ŠÒæM°=ÕÌi*±€ Þ² 1‘Ž=qŸj†ãQ¾yæ»ŠA–,2œcR;ãwáÅfÊÈìT©#æä`žø jšøŒ59¾H·¯VÕÕûëçÚÝyµA9Ó‹Ñ?Çúþºš—QÇ ÔvòßNqù«¼!ç‚¹äç¿C»=:Öš#m#bYã†ð¦/(œúŒtè Qž CÍÂÉ¶ž ÇVB ž2ONOZrA óAÇf^3–÷ÉéÁëÇç\ó«·äƒütéß_-Ï¦nJ[/Ì|2Ï#[Ù–!’,Oä‘Ç|sVâ±Ô/|´–Iœ˜î$àc®Fwt+Ûø¿zÏTšyLPZ>#a· ^r7d\u ©¢•âÈ3 83…ˆDTœ’@rOéÐW†ÁP”S”Ü£ó[‰ÚßŽÚ;éÕNŒW“kîüÊ ¨"VHlí×>ZÜ nwÝÏ ›¶ìqÎ×·Õel¿,³4Æ4`;/I'pxaœÔñ¼";vixUu˜’¸YÆ1×#®:Ž T–ñÒ[{Kwi mð·šÙ99Î cÏ#23É«Ÿ-Þ3ii¶©»ÒW·•×~Ôí£Óúô- »yY Ýå™’8¤|c-ó‚<–þ S#3Ì‰q¡mÜI"«€d cqf üç× #5PÜý®XüØWtîßy¹?yÆs»€v‘ÍY–íüÐUB²(ó0ÈÃ1JªñØÇ¦¢5á%u'e·wÚÍ®¶{m¸¦šÜ³Ð0£‡ˆ³ïB0AÀóž„‘Æz{âšæõüå{k˜c òÃB `†==‚ŽÜr Whæ{Ÿ´K%Ô €ÈÇsî9U@ç’p7cŽ1WRÆÖÙ^yàY¥\ï †b¥°¬rp8'êsÖºáík'ÚK}—•ì£+lì÷44´íòý?«Ö÷0¤I"Ú³.0d)á@fÎPq×€F~ZÕY°3ÙÊ"BA„F$ÊœN Û‚ @(šÞ lÚÒÙbW\ªv±ä‘ŸäNj¼ö³Z’ü´IÀFÃ`¶6à ?! NxÇÒ©Ò†Oª²½’·ŸM¶{êºjÚqŒ©®èþ ‰ ’&yL%?yÕÃ”®$•Ï\p4—:…À—u½ä‘°Ýæ$aCß”$ñŸoÄÙ>TÓù¦ƒÂKÆÅÉ@¹'yè{žÝ4ÍKûcíCì vŽ…y?]Ol©Ê|Íê¾Þ_;üÿ Ï¡Rçånÿ rÔ’[m²»˜¡Ž4ùDŽ›Ë) $’XxËëšY8¹i•†Á!‘þpJ•V^0 Œ±õèi²Å²en%·„†8eeù²Yˆ,S†=?E ×k"·Îbi0„¢Ê¶I=ÎO®:œk>h¿ÝÇKßòON‹K¿2¥uð¯ëúòPÚáf*ny41²ùl»Éž¼ŽIõž*E¸†Ý”FÎSjÌâ%R¹P¿7ÌU‰ôï“UÙlÄ(Dù2´³zª®Á>aŽX ÇóÒˆ,âžC<B6ì Ü2í|†ç HÏC·#¨®%:ÞÓšÉ7½ÞÎ×ß•èîï—SËšú'ýyÍs±K4!Ì„0óŒ{£Øs÷‚çzŒð¹ã5æHC+Û=¼Í}ygn0c|œðOAô9îkÔ®£ŽÕf™¦»R#copÛICžÃ©þ :ñ^eñ©ðe·”’´ø‘¦f å— # <ò3ïÖ»ðŸ×©Æ¤•Ó½»ï®ß‹·ôµ4ù'ý_ðLO‚òF‹®0 &Ü§˜œ0Œ0#o8ç#ô¯R6Û“yŽ73G¹^2½öò~o»Ÿ›##ÞSðr=ÑkÒ41º €–rØ ÷„ëƒëÎ zõo7"Ýà_=Š©‰Éldà`†qt÷+‹?æxù©%m,ö{.¶jú;%÷hÌ*ß›Uý}Äq¬fp’}¿Í¹ ü¼î Ïñg$ý*{XLI›•fBÀ\BUzr€Œr#Ð€í¥ÛÍ+²(P”x›$ÅèçœŒž tëÐÕkÖ9‘ab‡Ïò³œã#G'’¼o«U¢ùœ×Gvº4µ¾vÕí}½œ¢ïb{{)¥P’ÊÒº#«Bç˜€8Êä6GË”dTmV³$g¸i&'r:ƒ¬1œàòœãƒÒ • rñ¤P©ÑØô*IÆ[ ÝÏN¸Î9_³[™#Kr.Fí¤í*IÁ?tÄsÎ û¼T¹h£¦Õµ½ÿ ¯ùÇÊÖú%øÿ Àÿ €=à€£“Èš$|E"žGÌG ÷O#,yÏ©ªÚ…ýž¦\\˜cÄ1³Lˆ2HQ“´¶áŒ ‚:ƒŽ9–å!Š–Í‚É¾F''‘÷yÇNüûãëpÆ|=~¢D•äµ•vn2„sÓžGLë IUP´Uíw®Ú-/mm£²×Ì–ìíeý]? øÑüa¨ÞZÏeki,q‰c10PTpAÜÀg%zSß°2Ä¤¡U]®ØŠÜçžI;€èpx?_øZÊ|^agDóí¹ )ÊžßJö‰¡E]È##ço™NO÷¸ÈÇÌ0¹9>™¯Sˆ°pÃc°ŠI¤÷õ¿å}Ë¯ JñGžÿ ÂÀ+ãdÒc³Qj'ÅØîs&vç6îíŽë»iÞbü” ‚Â%\r9àg·ùÍxuÁüMg~ŸÚÁÎÜ²çŽ0?*÷WšÝ^O*#†€1èwsÎsùRÏpTp±¢è¾U(«u}íùŠ´R³²ef À9³bíÝ¿Ùéì ùïíÌóÅ1ý–F‘œ‘åà’9Àç9ëÒ‹)ˆ”©±eÎ c×sù×Î{'ÎâÚõéßuOÁœÜºØ‰fe“e6ñžyäöÀoÆ§²‹„•%fˆ80(öåO½Oj…„E€T…%rKz°Î?.;{šXÙ‡ŸeUÚd!üx9þtã%wO_øoòcM- j–ÒHX_iK#*) ž@Ž{ôÇ½Bd¹‰RÝn–ê0«7Ë†ìyÀ÷Í@¬Ì¢³³’ 9é÷½?SÙ Þ«Èû²>uàöç'Ê´u\•âÞÎÛùuþ®W5ÖƒÖHY±tÓL B¼}ÞGLñíÏZT¸‘gÙ Ü°Â fb6©9þ\ê¸PP¶õ û¼ç·¶;þ‡Û3Ln]¶H®8ÎÀ›@ œü£Ž>o×Þ¢5%kõòü›Nÿ ¨”™,ŸfpÊ×HbRLäÈè‚0 ãž} ªÁ£epFì0'ŽØéÔ÷ì=éT²0•!…Îzt9ç¾?”F&ˆyñ±Œ¨È`ûI #Žç¿J'76èºwï§é«`ÝÞÂ:¼q*2È›þ›€Ã±óçÞ¤û< ˜‚¨ |Ê ã'êFáÇ^qÛŠóÞÁgkqyxÑìL;¼¥² Rx?‡¯Y7PŽwnù¶†û¾ÜÂ·.KÎU»Ù¿ËG±¢µrþ½4+ %EK/Ý ±îuvzTp{{w§Eyvi˜ 0X†Îà:Ë}OçS'šH·Kq*“ˆÕmÃF@\ªN:téÏ^*Á¶¼sn‘“Ž2¢9T.½„\ýò@>˜7NFïNRÓ·wèôßEÕua'¬[þ¾cö¡ÌOæ¦âÅŠ². Ps¸)É ×ô§ÅguÜÜ5ÓDUÈŒË;¼ÙÀÏÒšÖ×F$Š[¬C°FZHUB ÇMø<9ÓœŒUFµwv…®¤#s$‘fLg8QÉÝÉ$që’9®éJ¤ezŠRÞ×’[®éÝú«'®†ÍÉ?zï¶¥³u3(’MSsŽ0Û@9$Ð…-‘ß¦O"§gŠ+¢n'k/ ‡“$±-µ°1–éÜôä)®ae ·2ÆŠ¾gÛ°Z¹#€r ¶9Ç|Õ¨âºŽÖIÑÖÜÇ»1Bc.çqÁR àûu®Š^Õ½Smkß}uzëmSòiõÒ<Ï×õ—£Îî6{ˆmŽåVUòãv3ü¤œqÐŒç“œô¶Ô¶¢‹{• b„ˆg©ù@ÇRTóÅqinÓ·ò×l‡1`¯+òŸ¶ÐqžÀ:fÿ Âi£häÙjz…¬wˆÄË™RI'9n½øãœv®¸ÓmªUÛ•ôI-_kK{ièßvim£Qµý|ÎoÇßìü-~Ú}´j:ÃÍŠ|¸˜¨ó× qŒŒžy®w@øßq%å½¶³imoj0¿h·F;8À,›¹¸üyu¿üO'|;´ðÄÚ¦Œ%:t„Fáß~÷O¿júß©a)ZV”ºÝïëëýjkÞHöfÔ&–î#ö«aðå'Œ’¥\™Il`õ¸9©dûLì ‹t‘ƒ¸ó"Ä€‘Ê7ÈÛŽ:vÜ ¯/ø1â`!»Ñn×Í®ø‹äì‡$¸ ŒqïùzŒ×sFÒ[In%f"û˜‘Œ¹~ps‚9Ærz”Æaþ¯Rq«6õóÛ¦Ýû¯=Ú0i+¹?ÌH¢VŒý®òheIÖr›7îf 8<ó×+žÕç[ÂÖ€]ÇpßoV%v© €pzþgµ6÷3í‹Ì’{²„äˆƒŒ‚Ìr8Æ1“Áë^{ñqæo Ø‹–¸2ý|ÇÜ¬¬Žr=;zþ¬ò¼CúÝ*|+[zÛ£³µ×ß÷‘š¨Ûúü®Sø&ì¬…˜Có[¶âÈ¼3ûÜ÷<ŒñØæ½WÈŸÌX#“3 "²ºÆ7Œ‘Üc¼‡àìFy5xKJŒ"îç.r@ï×Þ½Ä-ÿ þ“}ª}’*Þ!,Fm¸Î@†9b?1W{Yæ3„`Ú¼VõŠÚÛ_kùöG.mhÎñ ôíhí§Ô$.ƒz*(iFá’I^™$ðMUÓ|áíjéb[ËÆºo•ñDdŽà¸'“ŽA Ö¼ƒGÑµ/krG É–i\ôÉêNHÀÈV—Š>êÞ´ŠúR³ÙÈùÑõLôÜ9Æ{jô?°°Kýš¥WíZ¿V—m6·E}{X~Æ? zžÓæ8Ë¢“«¼ 39ì~¼ûÒÍ}žu-ëÇ•cÉåmÀÀÉ9Àsþ ”økâŸí]:[[ÍÍyhª¬w•BN vÏ$ôé‘Íy‹ü@þ"×ç¹ ¨v[Æ¼* ã zœdžµâàxv½LT¨T•¹7jÿ +t×ð·CP—5›=Î ¨/"i¬g¶‘#7kiÃç±'x9#Ž}êano!òKD‘ílï”('¿SÔð?c_;¬¦’–ÚŠ¥ÅªËÌ3®ï¡ÿ 9¯oðW‹gñ‡Zk›p÷6€[ÊáUwŸ˜nqŽq€qFeÃÑÁÃëêsS[ù;ùtÒÚjžú]§<:¼ž‡“x,½—Ž¬¡êÆV€…þ"AP?ãÛ&£vÂÅ»I’FÙ8ÛžÀ”œ¾ÜRÜÌ¬ŠÛÓ‘–Ä*›qôúŸÃAÀëßí-L¶š-™ƒµ¦i”øÿ g«|è*pxF:nžîË¯Þ¼¿þBŒÛQþ¿C»Š5“*]Qÿ „±À>Ý:ôä*D(cXÚ(†FL¡‰`çØÏ;þ5âR|Gñ#3î`„0+µmÑ€ún Þ£ÿ …‰â¬¦0 –¶ˆœ€¹…{tø?Ê¯(_çþ_Š5XY[¡Ù|Q¿ú µŠ2ï¸›sO* Ð‘ÿ ×â°<+à›MkÂ÷š…Ä³ ·Ü–ˆ«ò‚?ˆœúäc½øåunû]¹Iïåè› ç ¯[ð&©¥Ýxn;6>}²’'`IË0ÁèN}zö5éâ©âr\¢0¥ñs^Ml¿«%®ýM$¥F•–ç‘Øj÷Ze¦£k 2¥ô"FqÀ`„~5Ùü+Ò¤—QºÕ†GÙ—Ë‹ çqä°=¶ÏûÔÍcá¶¡/ˆ¤[ý†iK ™°"ó•Æp;`t¯MÑt}+@²¶Óí·Ídy’3mÕË‘’zc€0 íyÎq„ž ¬4×5[_]Rë{]ì¬UZ±p÷^åØÞÈ[©&OúÝÛ‚‚s÷zžIïßó btÎÎª\ya¾U;C¤t*IÎFF3Š¸™c 1žYD…U° êÄàõë\oŒ¼a ‡c[[GŽãP‘7 â znÈ>Ãü3ñ˜,=lUENŒäô¾ÚÀÓ[_ð9 œ´JçMy©E¢Àí}x,bpAó¦üdcûŒW9?Å[Há$¿¹pÄ™#^9O88©zO=«Ë!µÖüY¨³ªÍy9ûÒ1Â úôÚ»M?àô÷«ÞëÖ–ÙMÌ#C&ßnJ“Üp#Ð‚~²†G–àíekÏµío»_žŸuÎ¨Q„t“ÔÛ²øáû›´W6»Øoy FQÎr $Óõìk¬„‹ïÞÚ¼sÆíòÉ67\míÎyF¯ð¯TÓã’K;ë[ð·ld«7üyíšÉð¯Šµ êáeYžÏq[«&vMÀðßFà}p3ÅgW‡°8ØßVín›þšõ³¹/ ü,÷ií|’‘´R,®ŠÉ‡W“Ž1ØöëÓ¾xžÖÞ¹xÞÝ¬XZGù\’vŒž˜ÆsØúÓïí&ÒÒ{]Qž9£Ê¡ù·ÄÀ»¶áHäž™5—ìö« -&ù¤U<±ÉÆA>½ý+æg jžöë¥¢þNÛ=÷JÖÛfdÔ õýËúû‹ÓØB²¬fInZ8wÌÉÐ®~aƒÎ=3ìx‚+/¶äÁlŠ‚?™Æü#8-œ\pqTZXtè%»»&ÚÝ#´ŠðÜžã§Í’¼{p·ß{m>ÞycP¨’¼¢0ú(Rƒë^Ž ñó¼(»y%m´ÕÙ}ÊûékB1¨þÑ®,#Q)ó‡o1T©ÜÃ*Ž‹‚yö<b‰4×H€“ìÐ. ¤²9ÌŠ>„Žãøgšñ ¯Š~)¸ßå\ÛÛoBŒa·L²œg$‚Iã¯ZÈ—Æ~%”äë—È8â)Œcƒ‘Âàu9¯b%)ÞS²¿Ïïÿ 4Öºù}Z/[H%¤vÉ#Ì’x§†b © ³´tÜ{gn=iï%õªÇç]Ü§—!åw„SÓp ·VÈÏ¡?5Âcâb¥_Ä¤Šz¬—nàþÖÎŸñKÄöJé=ÌWèêT‹¸÷qÎáƒŸ•q’zWUN«N/ØO^Ÿe|í¾©k{üõ4öV^ïù~G¹êzÂèº|·÷×[’Þ31†rpjg·n Æ0Ý}kåË‹‰nîe¹ËÍ+™ÏVbrOç]'‰¼o®xÎh`¹Ç*±ÙÚ!T$d/$žN>¼Wqá¯…Z9ÑÒO\ÜÛê1o&,-z ~^NCgNÕéá)ÒÊ©7‰¨¯'Õþ¯þ_¿Ehîþóâ €ï¬uÛûý*ÎK9ä.â-öv<²‘×h$àãúW%ö¯~«g-ÕõÀàG~>Zú¾Iš+(šM³ Û#9äl%ðc¬ ûÝ xÖKG´x®|¸¤Ï™O:Ê8Ã’qÉcÔä‚yÇNJyËŒTj¥&µOmztjÿ ?KëaµÔù¯áýóXøãLeb¾tžAÇû`¨êGBAõ¾•:g˜’ù·,þhÀ`¬qÜ` e·~+å[±ý“âYÄjWì—µHé±ø?Nõô>½âX<5 Ç©ÏÑ¼M¶8cÜªXŽÉ^r?¼IróÈS•ZmÇ›™5»òÚÚ7ïu«&|·÷•Î† >[©ÞXHeS$Œyà€ ÷ù²:ò2|óãDf? Z¼PD¶ÓßC(xÆ0|©ßR;ôMsÿ µ´ÔVi¬,Í¹›Ìxâi˜`¹,GAéÇlV§ÄýF×Yø§ê–‘:Ã=ò2³9n±ÉžØÏ@yÎWžæ±Ãàe„ÄÒN ]ïòêìú_Go'¦ŽÑ’_×õÐ¯ðR66þ!›ÑÄ gFMÙ— äžäqôÈ;ÿ eX<#%»Aö‰ãR¤ Í”Ž¹È G&¹Ÿƒ&á?¶Zˆ±keRè Kãnz·ãŠÕøÄÒÂ9j%@®×q±ÜŒý[õ-É$uíè&¤¶9zÇï·Oøï®ÄJKšÖìdü"µˆ[j×²Îc;ã…B(g<9nàÈ¯G½µŸPÓ.´Éfâ¼FŽP 31 ‘ÏR}<3šä~ Ã2xVöî Dr Ç\›}Ý#S÷ÈÀëŽHÆI®à\OçKuäI¹†ó(”—GWî ñ³¹¸æ2¨›‹ºÚû%¾ýÖ_3ºNú¯ëúì|ÕÅÖ‰}ylM’ZËîTÿ á[ðÐñ/ˆ9Àû ¸ón3 MÃ²d‘÷ döª^.ÊñŽ°›BâîNp>cëÏçÍzïÃôÏ YÍ%ª¬·ãÏ-*9ÜÂãhéŒc¾dÈêú¼Ë,. VŠ÷çeÿ n/¡¼äãõâ=‹xGQKx”|¹bÌŠD@2Œ 8'Ž àúƒŽ+áDÒ&¡¨"Œ§–Žr22 Ç·s]ŸÄ‹«ð%ÚÄ<¹ä’(×{e›HÀqÁç©Ç½`üŽÚõKé¥š9ƒÄ±€<–úƒú~ çðñO#Í%iKKlµ¦¾F)'Iê¬Î+Ç(`ñ¾£œdÈ’`™ºcßéé^ÿ i¸”Û\ý¡æhÔB«aq¸}ãÀÆ:ÜWƒ|FÛÿ î©±BŒÇÀeaŸ-sÊ€:úW½ÜÝÜ<%$µ†%CóDªÀí%IÈÏÊ¤…ôäñÞŒ÷‘a0“ôŽÚë¤nŸoW÷0«e¶y'Å»aÎ—2r’# Û°A^ý9ÉQÔõ=ù5¬£Öü.(Þ’M$~V«=éSÄFN½®©ÔWô»ÿ þHžkR‹ìÏ+µµžöê;khÚI¤m¨‹Ôš–âÖçJ¾_Z•’6a”Èô> ÕÉaÕ<%®£2n bQŠå\tÈõUÿ ø»þ‹k15‚ÃuCL$Ý¹p P1=Oøýs¯^u éEJ”–éêŸê½5ýzy›jÛ³á›Ûkÿ ÚOcn±ÛÏîW;boºz{ãžüVÆ¡a£a5½äÎÂks¸J@?1è¿{$ä‘=k”øsÖ^nŒ¦)ÝåXÃíùN1ØõÚOJë–xF÷h¸ Œ"Ž?xäœšü³ì¨c*Fœ¯i;7~ñí×«Ðó¥Ë»3Ãü púw ‰°<Á%»ñž ÿ P+Û^ ¾Ye£ŽCÄŒ„/>˜>•á¶Ìm~&&À>M[hÈÈÿ [Ž•íd…RO@3^Ç(Ê½*¶ÖQZyßþ 1Vº}Ñç?¼O4Rh6R€ª£í¡ûÙ a‚3ß·Õ ü=mRÍ/µ9¤‚0ÑC¼Iè:cŽsÛ¾™x£ÆÐ¬ªÍöË¢ìƒ’W$•€Å{¨ÀPG ÀÀàŸZìÍ1RÉ0´ðxEË9+Éÿ ^rEÕ—±Š„70l¼áË@û.' ¼¹Žz€N3úUÉ<3á×*?²¬‚ä†"Ùc=p íÛ'¡ª1ñ"økJ†HÒ'»Ÿ+ oÏN¬Ã9 dÙãÜ×“ÏâÍ~æc+j·Jzâ7(£ðW]•æ™?nê´º6åwéåç÷N•ZŠíž›¬|?Ðõ?Ñ-E…Â®³ÇV$~X¯/…õ x‘LˆÑÜÚÈ7¦pzãÜüë½ðÄ^õtÝYËÍ7ÉÖÕ8ÏUe# #€r=sU¾/é’E§jRC4mxNÝ´9†íuá»›V‘ ZI€×cr1Ÿpzsøf»¨åV‹ìû`qËLÊIã?\~¼³áËC©êhªOîO»‘ÃmçÛçút×¢x“Z}?Ãœê#b-¤X7õÄò gž zzbº3œm*qvs·M=íúéw}¿&Úª°^Ö×µÏ(ø‡â†Öµƒenñý†×åQáYûœ÷ÇLœôÎNk¡ðÂ‡¼/µ¸n0æÉ0¬ƒ‚üîÉÆvŒw®Sáö”š¯‹-üÕVŠØÙ[$`(9cqƒÔ_@BëqûÙ`Ýæ0;79È?w<ó |ÙÜkßÌ1±Ëã¿ìÒ»ðlìï«ÓnªèèrP´NÏÂš&ŽéöÙ¸÷æ°~-_O'‰`°!RÚÚÝ%]Ø%þbß1'¿ÿ XÕáOöÎŒ·‹¬+Åæ*ÛÛ™0¤ƒOÍÔ`u¯¦ÂaèÐÃÓ«‹¨Ô¥µœ¿¯ÉyÅÙ.oÔôŸ Úx&(STðÝ½¦õ] ’ÒNóÁäÈùr3í·žÚ[™ƒ¼veÈÃ·ÞIõÎGlqÎ=M|«gsªxÅI6 ]Z·Îªä,¨zŒŽÄ~#ØŠúFñî™ªiÉqc©éÐD>Së”‘ GñŽ1éÐ^+ Ëi;Ô„µVÕú»i¯ÈÒ-ZÍ]òÜ˜®ì`bÛÙ¥_/y(@÷qÐúg Ô÷W0.Ø› 6Ò© r>QƒŒ0+Èîzb¨É+I0TbNñ"$~)ÕÒ6Þ‹{0VÆ27œWWñcÄcX×íôûyKZéðªc'iQ¿¯LaWŠŸS\·Š“ÅºÊ¸…ôÙÂí|öÀÇåV|!¤ÂGâÛ[[’ï 3OrÙËPY¹=Î1õ5öåTžÑè Ú64/üö?Zëžk}¬¶éàoá¾á}3“ü]8Éæ¿´n²Žš_6¾pœ)2?úWÓÚ¥¾¨iWúdŽq{*ª1rXŒd…m»‰äcô¯–dâ•ã‘Jº¬§¨#¨®§,df«8ÉÅßN¾hˆ;îÓ=7áùpën®É 6ûJžO2^œÐò JÖø¥²ãÂ›Ò6Ü·‰!wbÍ‚¬O©»õ¬ÿ ƒP=Ä:â¤-&ÙŽ `È9 r9íÏ§zë> XÅ7ƒ5X–krÑ¢L7€ìw}ÑŸNHëŒüþ:2†á¼+u·á÷N/Û'Ðç~ß˜ô«ëh!ónRéeQ´6QÛÿ èEwëÅÒ|¸Yqó1uêyùzð8 ƒŠù¦Ò;¹ä6öi<'ü³„[ÃZhu½ ùÍ¡g‚>r¯×ŠîÌx}bñ2“kê£§oø~›hTèóËWò4|ki"xßQ˜Ï6øÀLnß‚0 ¹Æ{±–¶Öe#¨27È@^Ìß.1N¾œyç€õ†ñeé·Õã†çQ°€=Ì©ºB€Ø8<‚ÃSõ®ùcc>×Ú .Fr:žÝGæ=kÁâ,^!Fž ¬,àµ}%¶«îõ¹†"r²ƒGœüYÕd?aÑÃY®49PyU ÷þ!žxÅm|/‚ãNð˜¼PcûTÒ,¹/Ý=FkÏ|u¨¶«âë…{¤m¢]Û¾ïP>®XãÞ½iÓÁ¾ ‰'¬–6ß¼(„ï— í!úÙäzôë^–:œ¨å|,_¿&š×]uÓÑµÛô4’j”bž§x‘Æ©ã›á,‚[Ã” ÎÞ= î®ˆŒËæ ÀùYÁ?ŽïÚ¼?ÁªxºÕÛ,°1¸‘¿ÝäãØ¯v…@¤åq½ºã œàûââ·z8Xýˆþz~—û»™âµj=Ž â~ãáh@'h¼F#·Üp?ŸëQü-løvépx»cŸø…lxâÃûGÂ·‰¶ø”L£©%y?¦úõÆü-Õ¶¥y`Òl7>q’2üA?•F}c‡jB:¸Jÿ +§¹¿¸Q÷°ív=VÑìu[Qml%R7a×IèTõéŽx¬ ?†š7 1†îã-ˆã’L¡lŽ0OÓ=ÅuˆpÇ•¼3ÛùÒ¶W/!|’wŽw^qÔ×ÏaóM8Q¨ãÑ?ëï0IEhÄa¸X•`a ?!ÐñùQ!Rä ÂžqŽžÝO`I0ÿ J“y|ñ!Îã@99>þ8–+éáu…!ù—ä Ê°<÷6’I®z ÅS„¾)Zþ_Öýµ×ËPåOwø÷þ*üïænÖùmØÝûþ¹=>¦½öî×Jh]¼ç&@§nTŒ6ITÀõ^Fxð7Å3!Ö·aÛ$þÿ ¹ã5îIo:ÈªmËY[’8ÇÓ¾Ç‰*òû¢¥xõ¾¼ú•åk+\ð¯ HÚoŽl•Ûk,¯ ç²²cõÅ{²Z\ ´ìQ åpzŽ3Ôð}ÿ Jð¯XO¡øÎé€hÙ¥ûLdŒ`““ù6Gá^ÃáÝ^Ë[Ñb¾YåŒÊ»dŽ4†2§,;ÿ CQÄ´¾°¨c–±”mºV{«ßÕýÄW\ÖŸ‘çŸ,çMRÆí“l-ƒn~ë©ÉÈê Ü?#Ž•¹ðãSÒ¥ÐWNíà½;ãž)™ÎSÈ9cóLjëµ¿Å«iÍk¨ió¶X‚7÷ƒ€yãnyÏŽëÞ Öt`×À×V's$È9Ú:ä{wÆEk€«†Çàc—â$éÎ.éí~Ýëk}ÅAÆpörÑ¢‡Šl¡ÑüSs‹¨‰IÃ„óÀ×wñ&eºðf™pŒÆ9gŽTø£lñëÀçŽ NkÊUK0U’p ï^¡ãÈ¥´ø{£ÙHp`’ØåbqÏ©äó^Æ: Ž' ÊóM«õz+ß×ó5Ÿ»('¹ð¦C„$˜Å¢_ºÈI?»^äã'ñêzž+ë€ñ-½»´}¡Ë*õ?.xÇ^1ŽMyÇÂ¸&“Â—L–îëöâ7…' bqéÎGé]Ëªâ1$o²¸R8Ã`.q€}sÖ¾C98cêÆÞíïóòvÓòùœÕfÔÚéýuèÖ·Ú Å‚_¤³ÜÛºÆ‘ÃŸ”à×¨ý:×ƒxPþÅÕî-/üØmnQìïGÎŠÙRqê=>¢½õnæ·r!—h`+’;ò3È<“Û©éšóŸx*÷V¹¸×tÈiˆßwiÔÿ |cŒñÏ®3Ö½Ì°‰Ë Qr©ö½®¼ÛoÑÙZÅÑ«Oàµ¯ýw8;k›ÿ x†;ˆJa;‘º9÷÷R+¡ñgŽí|Iáë{ôáo2Ê²9 029ÉÏLí\‰¿¸Ÿb˜ "Bv$£&#ßiê>=ªª©f ’N ëí>¡NXW~5×úíø\‰»½Ï^ø(—wÖú¥¤2íŽÞXæÁ$°eÈ888^nÝë²ñÝÔ^ ÖÚ9Q~Ëå7ï DC¶ÑµƒsËÇè9®Wáþƒ6‡£´·°2\Ý:ÈÑ?(#¨'$õèGJ¥ñW\ÿ ‰E¶—¸™g˜ÌÀ¹;Pv ú±ÎNs·ëŸ’–"Ž/:té+ûË]öJöÓM»ëø˜*‘•^Uý—êd|‰åñMæÔÝ‹23å™6æHùÛ‚ëüñ^…ñ1¢oêûÑEØ.õ7*ÅHtÎp{g<·Á«+¸c¿¿pÓ¾Æby=8É_ÄsÆk¬ñB\jÞÔì••Ë[9Píb‹Bãƒ… =93§ð§LšÛáÖšÆæXÌÞdÛP.0\ãïÛ0?™úJ¸™Ë ”•œº+=<µI£¦í¯õêt¬d‹T¬P=ËFêT>ÍØØ@Ï9<÷AQÌ×»Õ¡xùk",JÎæù±Éç$œŽŸZWH®¯"·UÌQÂ ’ÙÈ]ÅXg<ã ß¨g3-Üqe€0¢¨*Œ$Üƒ ’Sû 8ãŽ¼_/e'+Ï–-èÓ¶¶Õíß[·ÙÙ½îì—¼sk%§µxä‰â-pÒeÆCrú ôÏƒžû=”šÅô(QW‚Õd\ƒæ. \àö¹¯F½°³½0M>‘gr÷q+œ¶NïºHO— ¤ Ü¥Ý”n·J|ÆP6Kµc=Isó}Ò çGš)a=—#vK›åoK§ßóÙ¤¶¿õú…ÄRÚ[ËsöÙ¼Ë•Ë ópw®qœŒ·Ø ùÇâ‹ý‡ãKèS&ÞvûDAù‘É9ŒîqÅ} $SnIV[]Ñ´Ó}ØÜ¾A Ü|½kÅþÓ|EMuR¼.I¼¶däò‚ÃkÆ}ðy¹vciUœZ…Õõ»z¾÷¿n¦*j-É/àœHã\y5 Û ß™ó0—äŸnzôã#Ô¯,†¥ÚeÔ÷ÜÅ´„“'c…<íÝ€<·SŠ¥k§Ã¢éÆÆÙna‚8–=«Êª[Ÿ™°pNî02z“ÔÙ–K8.È’Þî(vƒ2®@ äÈûãçžxäÇf¯ˆu¹yUÕîýWšÙ|›ëÒ%Q^í[æ|éo5ï‚¼ZY•^{96ˆY‚§v*x>âº_|U¹Ö´©tûMÒÂ9PÇ#«£#€ éÉñ‘ƒÍz/‰´-Ä¯¹°dd,Ð‘›p03ƒœ{ç9=+ Ûá§‡¬¦[‡‚êå©º¸#±ß=³ý¿•Õµjñ½HÙh›Û[§ÚýÊöô÷{˜?ô÷·Ô.u©–_%còcAÀ˜’ }0x9Î>žñÇáÍ9,ahï¦Ì2òÓ ñÛAäry$V²Nð ]=$Ž ‚#Ù‚1ƒƒødõMax‡ÂÖ^!±KkÛ‘ «“Çó²FN8+ëÎ{Ò¼oí§[«ÕMRoËeç×[_m/¦¦k.kôgŽxsSÓ´ý`êzªÜÜKo‰cPC9ÎY‰#§^üý9¹âïÞx£Ë·Ú`±‰‹¤;³–=ÏaôÕAð‚÷kêÁNBéÎælcõö®£Fð†ô2Ò¬]ßÂK$ÓÜ®•”/ÊHàã$ä¸÷ëf¹Oµúâ“”’²øè´µþöjçNü÷üÌ¿ xNïFÒd»¼·h®îT9ŽAµÖ>qÁçÔœtïÒ»\È¶ÎîcÞäîó3¶@#ÉIÎ ÔñW.<´’¥–ÑÑ€ÕšA‚ ;†qÓë‚2q ÒÂó$# Çí‡ !Ë}Õ9ÈÎÑÉã=;ŒÇÎuñ+ÉûÏ¥öíeÙ+$úíÜå¨¯'+êZH4ƒq¶FV‹gïŒ208ÆÌ)íÐ±>M|÷âÍãÂ¾"iì‹¥£Jd´™OÝç;sÈúr+ÜäˆË)DŒ¥šF°*3Õ”d{zÔwºQ¿·UžÉf†~>I+ŒqÔ`ð3œ“Ü×f]œTÁÔn4“ƒø’Ýßõ_«*5šzGCÊ,þ+ê1Ã²÷O¶¸cœºb2yÇ;cùÕ£ñh¬›áÑŠr¤ÝäNBk¥—á—†gxšX/ì‘˜hŸ*Tçn =ûã¦2|(ð¿e·ºÖ$ ýìŸ!'åÎ°yîî+×öœ=Y:²¦ÓÞ×iü’—ü -BK™£˜›âÆ¡&véðõ-ûÉY¹=Onj¹ø¯¯yf4·±T Pó`çœ7={×mÃ/¢˜ZÚòK…G½¥b„’G AãÜœ*í¯Ã¿ IoæI¦NU8‘RwÈã;·€ Û×ëÒ”1Y •£E»ÿ Oyto¢<£Áö·šï,ä‰§ûA¼sû»Nò}¹üE{ÜÖªò1’õÞr0â}ÎØ#>à/8ïéÎ~—áÍ#Ã±Îlí§³2f'h”?C÷YËdð:qëõÓ·‚ïeÄ© ÔÈØÜRL+žAÎ3¼g=åšó³Œt3 ÑQ¦ùRÙßE®¼±w_;þhš’Sirÿ ^ˆã¼ià©‡|RòO„m°J/“$·l“ ÇÓ¿ÿ [ÑŠÆ“„†Õø>cFÆ6Ø1ƒ– àz7Ldòxäüwá‹ÝAXùO•Úý’é®ähm •NÀ±ÌTÈç ƒ‘I$pGž:‚ÄbêW¢®œ´|¦nÍ>¶ÖÏ¢§ÎÜ¢ºö¹•%ÄqL^öÛKpNA<ã¡ …î==ª¸óffËF‡yÌcÉ ©ç$ð=ñÏYþÊ’Ú]—¥‚¬‚eDïÎH>Ÿ_ÌTP™aÂ‰ch['çÆÜò7a‡?w°Ïn§âÎ5”’¨¹uÚÛ|´ÓÓc§{O—ü1•ªxsÃZ…ÊÏy¡Ã3¸Ë2Èé» ‘ƒÎ äžÜðA§cáOéúÛ4ý5-fŒï„ù¬ûô.Ç Üsž•Ò¾•wo<¶Ÿ"¬¡º|£ î2sÇ¡éE²ÉFÑ±rU°dÜ6œ¨ mc†Îxë×ºÞ'0²¡Rr„{j¾í·è›µ÷)º·å–‹î2|I®Y¼ºÍË·–ÃÆàã£'óÆxƒOÆÞ&>\lóÌxP Xc¸ì Sþ5§qà/ê>#žÞW¸if$\3 ® ûÄ“ùŽÕê¾ð<Ó‹H¶óÏ" å·( á‘€:ã†8Ï=+ê¨¬UA×ÃËÚT’ÑÞöù¥¢]{»ms¥F0\ÑÕ—ô}&ÛB´ƒOŽÚ+›xíÄÀ1 ,v± žIëíZ0Ç§™3í2®0à¸—p9öÝÔž)ÓZËoq/Ú“‘L ²ŒmùŽï‘Ó9§[Û#Ä‘\ÞB¬Çs [;à à«g‚2ôòªœÝV§»·¯/[uó½õÛï¾ /šÍ}öüÿ «=x»HŸÂÞ.™ ÌQùŸh´‘#a$‚'¡u<Š›Æ>2>+ƒLSiöwµFó1!eg`£åœ ÷ëÛö}Á¿ÛVÙêv $¬ƒ|,s÷z€ðÎƒ¨x÷ÅD\ÜŒÞmåÔ„ ˆ o| :{ÇÓ¶–òÁn!´0Ål€, ƒ ( ÛŒŒc¶rsšæ,4‹MÛOH!@¢ ÇŽ„`å²9ÝÃw;AÍt0®¤¡…¯ØÄ.Àìí´ƒ‘ßñ5Í,Óëu-ÈÔc¢KÃÓ£òÖÌºU.õL¯0…%2È—"~x ‚[`có±nHàŽyàö™¥keˆìŒÛFç{(Ø©†`Jã#Žwg<“:ÚÉ;M ^\yhûX‡vB·÷zrF?§BÊÔ/s<ÐÈB)Û± ·ÍÔwç5Âã:så§e{mÑ¤ï«Òíh—]Wm4âí¿ùþW4bC3¶ª¾Ùr$pw`àädzt!yŠI„hÂîàM)!edŒm'æ>Ç?wzºKìcŒ´¯Ìq6fp$)ãw¡éUl`µ»ARAˆÝÕgr:äŒgƒéé[Ôö±”iYs5Ýï«ÙG—K=þF’æMG«óÿ `ŠKÉ¦uOQ!ÕåŒ/ÎGÞ`@ËqÕzdõâ«Ê/Ö(ƒK´%ŽbMüåÜŸö—>¤óŒŒV‘°„I¢Yž#™¥ùÏÊ@8 œgqöö5ª4v×“[¬(q cò¨À!FGaÁõõ¯?§†¥ÏU½í¿WªZ$úyú½Žz×§Éþ?>Ã×È•6°{™™ŽÙ.$`ÎUœ…çè ' ¤r$1Ø(y7 ðV<ž:È ÁÎMw¾Â'Øb§øxb7gãÐž½óÉÊë²,i„FÈ¹£§8ãäÂ½k¹¥¦ê/ç{ïêï¦‡2œ/«ü?¯Ô›ìñÜ$þeýœRIåŒg9Ác’zrrNO bÚi¢ ÑºË/$,“ª¯Ýä;Œ× ´<ÛÑn³IvŸb™¥ nm–ÄŸ—nÝÀãŽ3ëÍG,.öó³˜Ù£¹uÊÌrŠ[<±!@Æ:c9ÅZh ì’M5ÄìÌ-‚¼ëÉùqŽGì9¬á ;¨A-ž—évþÖ–^ON·Ô”ŸEý}ú×PO&e[]ÒG¸˜Ûp ƒÃà/Ë·8ûÀ€1ž@¿ÚB*²¼ñì8@p™8Q“žÆH'8«I-%¸‚ F»“åó6°Uù|¶Ú¸ã ò^Äw¥ŠÖK–1ÜÝK,Žddlí²0PÀü“×ükG…¯U«·¶–´w¶ŽÍ¾©yÞú[Zös•¯Á[™6° ¨¼ÉVæq·,# ìãï‘×8îry®A››¨,ãc66»Ë´ã'æÉù?t}¢æH--Òá"›|ˆ¬[í 7¶ö#¸9«––‹$,+Ëqœ\Êøc€yê^Ý¸Äa°«™B-9%«×®‹V´w~vÜTéê¢·þ¼ˆ%·¹• ’[xç•÷2gØS?6åÀÚ õ9É#š@÷bT¸º²C*3Bá¤òÎA9 =úU§Ó"2Ãlá0iÝIc‚2Î@%öç94ùô»'»HÄ¥Ô¾@à Tp£šíx:úÊ:5eºßMý×wµ›Ó_+šº3Ýyvÿ "ºÇ<ÂI>Õ1G·Ë«È«É# àÈÇ øp Jv·šæDûE¿›†Ë’NFr2qŸ½ÇAÜšu•´éí#Ä¦8£2”Ú2Ã/€[ÎTr;qŠz*ý’Îþ(â‰ ;¡TÆâ›;ºÿ àçœk‘Þ8¾Uª¾íé{^×IZéwÓkXÉûÑZo¯_øo×È¡¬ â–ÞR§2„‚Àœü½ùç® SVa†Âüª¼±D‘ŒísŸàä|ä2 æ[‹z”¯s{wn„ÆmáóCO+†GO8Ïeçåº`¯^¼ðG5f{Xžä,k‰<á y™¥voÆ éÛõëI=œ1‹éíÔÀÑ)R#;AÂncäŽ:tÏ#¶TkB.0Œ-ÖÞZÛgumß}fÎJÉ+#2êÔP£žùÈÅi¢%œ3P*Yƒò‚Aì“Ž2r:ƒÐúñiRUQq‰H9!”={~¼“JŽV¥»×²m.ÛßºiYl¾òk˜gL³·rT• ’…wHÁ6ä`–Î3ùÌ4Øe³†&òL‘•%clyÃ®AÂäà0 žüç$[3uÅ˜î¹•pNOÀÉ=† cï{rYK ååä~FÁ •a»"Lär1Ó¯2Äõæ<™C•.fÕ»è¥~½-¿g½Â4¡{[ør¨¶·Žõäx¥’l®qpwÇ»8ärF \cŽ¸ÜÆÓ-g‚yciÏÀ¾rÎwèØÈ#o°Á9ã5¢šfÔxÞæfGusÏÌJÿ µ×œ/LtãÅT7²¶w,l É³;”eúà·¨çîŒsÜgTÃS¦^ '~‹®›¯+k÷ZÖd©Æ*Ó[Ü«%Œk0ŽXƒ”$k#È¨ P2bv‘ƒŸáÇ™ÆÕb)m$É*8óLE‘8'–ÜN Úyàúô+{uº±I'wvš4fÜr íì½=úuú sFlìV$‘ö†HÑù€$§ õ=½¸«Ž] :Ž+•¦ïmRþ½l´îÊT#nkiøÿ _ðÆT¶7Ò½ºÒ£Î¸d\ã8=yãŽÜäR{x]ZâÚé#¸r²#»ÎHÆ6õ ç® ÎFkr;sºÄ.&;só±Ç9êH÷ýSšÕtÐU¢-n Ì| vqœ„{gŒt§S.P‹’Ž‰_[;m¥ÞZýRûÂX{+¥úü¼ú•-àÓ7!„G"“´‹žƒnrYXã¸îp éœ!ÓoPÌtÑ (‰Þ¹é€sÓ#GLçÕšÑnJý¡!‘Tä#“ß?îýp}xÇ‚I¥Õn#·¸–y'qó@r[ Êô÷<ÔWÃÓ¢áN¥4Ô’I&Ý¼¬¬¼ÞºvéÆ FQV~_ÒüJÖÚt¥¦Xá3BÄP^%ÈÎW-×c¡ú©¤·Iþèk¥š?–UQåIR[’O 5x\ÉhÆI¶K4«2ùªŠŒ<¼óœçØ`u«‚Í.VHä€ Ëgfx''9ÆI#±®Z8 sISºku¢ßÞ]úk»Jößl¡B.Ü»ÿ MWe °·Ž%šêÉ†¼»Âù³´œ O¿cÐÓÄh©"ÛÜÏ.ÖV’3nüÄmnq[ŒòznšÖ>J¬òˆæ…qýØP Ž:ä7^0yëWšÍ_79äoaÈ °#q0{ää×mœy”R{vÒÞ¶ÚÏe¥“ÚÆÐ¥Ì®—õýjR •íç›Ìb„+JyÜØÙ•Ç]¿Ôd þËOL²”9-Œ—õÃc'æÝ×œçÚ²ìejP“½ âù°¨†ðqòädÐƒÉäÖÜj÷PÇp“ÍšŠå«‘î <iWNsmª»¶vÓz5»ûì:Rs\Ðßôû×uÔÿÙ