This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author santoso.wijaya
Recipients michael.henry, r.david.murray, santoso.wijaya
Date 2011-03-18.18:19:09
SpamBayes Score 0.0043248935
Marked as misclassified No
Message-id <1300472350.08.0.509221880596.issue11589@psf.upfronthosting.co.za>
In-reply-to
Content
Do we need each sample--(input -> expected output)--to be its own unittest function?

Why not something like (pseudo-code):

expected = {
  'input1': 'output1',
  'input2': 'output2',
}

def test_encode(self):    # collapse all
    for input, output in expected.items():
        self._encode(input, output)    # test logic
History
Date User Action Args
2011-03-18 18:19:10santoso.wijayasetrecipients: + santoso.wijaya, r.david.murray, michael.henry
2011-03-18 18:19:10santoso.wijayasetmessageid: <1300472350.08.0.509221880596.issue11589@psf.upfronthosting.co.za>
2011-03-18 18:19:09santoso.wijayalinkissue11589 messages
2011-03-18 18:19:09santoso.wijayacreate