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 michael.foord
Recipients Yaroslav.Halchenko, abingham, brian.curtin, exarkun, fperez, michael.foord, nchauvat, ncoghlan, pitrou, r.david.murray
Date 2011-07-20.14:03:25
SpamBayes Score 2.3112e-06
Marked as misclassified No
Message-id <>
*If* we add this to unittest then we need to decide between test load time parameterised tests and test run time parameterisation. 

Load time is more backwards compatible / easier (all tests can be generated at load time and the number of tests can be known). Run time is more useful. (With load time parameterisation the danger is that test generation can fail so we need to have the test run not bomb out in this case.)

A hack for run time parameterisation is to have all tests represented by a single test but generate a single failure that represents all the failures. I think this would be an acceptable approach. It could still be done with a decorator.
Date User Action Args
2011-07-20 14:03:26michael.foordsetrecipients: + michael.foord, exarkun, ncoghlan, pitrou, r.david.murray, brian.curtin, fperez, Yaroslav.Halchenko, nchauvat, abingham
2011-07-20 14:03:26michael.foordsetmessageid: <>
2011-07-20 14:03:25michael.foordlinkissue7897 messages
2011-07-20 14:03:25michael.foordcreate