Databases
StackOverflow2013
Postsdbo
PORun Python unittest so that nothing is printed if successful, only AssertionError() if fails
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORun Python unittest so that nothing is printed if successful, only AssertionError() if fails
    primarykey
    data
    text
    <p>I have a test module in the standard unittest format</p> <pre><code>class my_test(unittest.TestCase): def test_1(self): [tests] def test_2(self): [tests] etc.... </code></pre> <p>My company has a proprietary test harness that will execute my module as a command line script, and which will catch any errors raised by my module, but requires that my module be mute if successful.</p> <p>So, I am trying to find a way to run my test module naked, so that if all my tests pass then nothing is printed to the screen, and if a test fails with an AssertionError, that error gets piped through the standard Python error stack (just like any other error would in a normal Python script.)</p> <p>The <a href="http://docs.python.org/library/unittest.html" rel="nofollow">docs</a> advocate using the unittest.main() function to run all the tests in a given module like</p> <pre><code>if __name__ == "__main__": unittest.main() </code></pre> <p>The problem is that this wraps the test results in unittest's harness, so that even if all tests are successful, it still prints some fluff to the screen, and if there is an error, it's not simply dumped as a usual python error, but also dressed in the harness.</p> <p>I've tried redirecting the output to an alternate stream using</p> <pre><code>with open('.LOG','a') as logf: suite = unittest.TestLoader().loadTestsFromTestCase(my_test) unittest.TextTestRunner(stream = logf).run(suite) </code></pre> <p>The problem here is that EVERYTHING gets piped to the log file (including all notice of errors). So when my companies harness runs the module, it complete's successfully because, as far as it can tell, no errors were raised (because they were all piped to the log file).</p> <p>Any suggestions on how I can construct a test runner that suppresses all the fluff, and pipes errors through the normal Python error stack? As always, if you think there is a better way to approach this problem, please let me know.</p> <p>EDIT:</p> <p>Here is what I ended up using to resolve this. First, I added a "get_test_names()" method to my test class:</p> <pre><code>class my_test(unittest.TestCase): etc.... @staticmethod def get_test_names(): """Return the names of all the test methods for this class.""" test_names = [ member[0] for memeber in inspect.getmembers(my_test) if 'test_' in member[0] ] </code></pre> <p>Then I replaced my call to <code>unittest.main()</code> with the following:</p> <pre><code># Unittest catches all errors raised by the test cases, and returns them as # formatted strings inside a TestResult object. In order for the test # harness to catch these errors they need to be re-raised, and so I am defining # this CompareError class to do that. # For each code error, a CompareError will be raised, with the original error # stack as the argument. For test failures (i.e. assertion errors) an # AssertionError is raised. class CompareError(Exception): def __init__(self,err): self.err = err def __str__(self): return repr(self.err) # Collect all tests into a TestSuite() all_tests = ut.TestSuite() for test in my_test.get_test_names(): all_tests.addTest(my_test(test)) # Define a TestResult object and run tests results = ut.TestResult() all_tests.run(results) # Re-raise any script errors for error in results.errors: raise CompareError(error[1]) # Re-raise any test failures for failure in results.failures: raise AssertionError(failure[1]) </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USjeremiahbuddha
    1. USjeremiahbuddha
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORun Python unittest so that nothing is printed if successful, only AssertionError() if fails
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PORun Python unittest so that nothing is printed if successful, only AssertionError() if fails
      1. USamyassin
      1. VTFavorite
    3. VO
      singulars
      1. PORun Python unittest so that nothing is printed if successful, only AssertionError() if fails
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload