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:28:34
SpamBayes Score 6.03741e-05
Marked as misclassified No
Message-id <>
So if we do import time *or* test load time parameterisation then we can do separate failure reporting. We may still want to improve "test selection" for parameterised tests.

There are use cases for run time parameterisation (for example generating tests from a database that is only available during the test run was one use case someone has that can't be met by early parameterisation).

If we do run time parameterisation then I think we can only maintain compatibility with existing uses of test suites by having a single test case instance per parameterised test, and single combined failure report.

I would prefer *not* to add run time parameterisation.
Date User Action Args
2011-07-20 14:28:35michael.foordsetrecipients: + michael.foord, exarkun, ncoghlan, pitrou, r.david.murray, brian.curtin, fperez, Yaroslav.Halchenko, nchauvat, abingham
2011-07-20 14:28:35michael.foordsetmessageid: <>
2011-07-20 14:28:34michael.foordlinkissue7897 messages
2011-07-20 14:28:34michael.foordcreate