Databases
StackOverflow2013
Postsdbo
POHow can I hide my stack frames in a TestCase subclass?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow can I hide my stack frames in a TestCase subclass?
    primarykey
    data
    text
    <p>I want to add a custom assert method to a <code>TestCase</code> subclass. I tried to copy my implementation from the <code>unittest</code> module so that it would match the behaviour of the regular <code>TestCase</code> as closely as possible. (I would prefer to just delegate to <code>self.assertEqual()</code> but this causes even more backtrace noise, see below.) The <code>unittest</code> module seems to automatically hide some internal details of its implementation when reporting failed assertions.</p> <pre><code>import unittest class MyTestCase(unittest.TestCase): def assertLengthIsOne(self, sequence, msg=None): if len(sequence) != 1: msg = self._formatMessage(msg, "length is not one") raise self.failureException(msg) class TestFoo(MyTestCase): seq = (1, 2, 3, 4, 5) def test_stock_unittest_assertion(self): self.assertEqual(len(self.seq), 1) def test_custom_assertion(self): self.assertLengthIsOne(self.seq) unittest.main() </code></pre> <p>The output of this is as such:</p> <pre><code>amoe@vuurvlieg $ python unittest-demo.py FF ====================================================================== FAIL: test_custom_assertion (__main__.TestFoo) ---------------------------------------------------------------------- Traceback (most recent call last): File "unittest-demo.py", line 16, in test_custom_assertion self.assertLengthIsOne(self.seq) File "unittest-demo.py", line 7, in assertLengthIsOne raise self.failureException(msg) AssertionError: length is not one ====================================================================== FAIL: test_stock_unittest_assertion (__main__.TestFoo) ---------------------------------------------------------------------- Traceback (most recent call last): File "unittest-demo.py", line 13, in test_stock_unittest_assertion self.assertEqual(len(self.seq), 1) AssertionError: 5 != 1 ---------------------------------------------------------------------- Ran 2 tests in 0.000s FAILED (failures=2) </code></pre> <p>Note that the custom assert method causes a stack trace with two frames, one inside the method itself, whereas the stock <code>unittest</code> method only has one frame, the relevant line in the user's code. How can I apply this frame-hiding behaviour to my own method?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USamoe
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow can I hide my stack frames in a TestCase subclass?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POHow can I hide my stack frames in a TestCase subclass?
      1. USkumar_m_kiran
      1. VTFavorite
    3. VO
      singulars
      1. POHow can I hide my stack frames in a TestCase subclass?
      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