Janus Dam Nielsen <[EMAIL PROTECTED]> writes: > I think that having parametrized tests is good, however I just > wanted to point out that defining the parameters in the Runtime > class/object might not be suffienciently expressive to what we want. > We might would like a kind of grouping/system of tests so that it is > easy to run the tests without any particular knowledge of which > protocols support which parameters. > > Those tests for which a given set of parameters is invalid, the test > could return an undefined value, or the test could be elided from > the set of tests since it doesn't make any sense for these > parameters anyhow.
The test suite is implemented using Trial, a Twisted tool which extends the standard Python unittest module with support for Deferreds. The Python unittest module is modelled after JUnit. In Trial there is support for marking a test as skipped, and that might be useful for what you are describing -- we could query the tests for their requirements and if they do not match the parameters of the current test, then we skip that test. Something like that could work, but I don't know if it is the best way... Have you looked at the Trial documentation to see how it could be done? There is a tutorial here: http://twistedmatrix.com/trac/browser/branches/trial-tutorial-2443/doc/core/howto/trial.xhtml?format=raw and the API documentation is here: http://twistedmatrix.com/documents/current/api/twisted.trial.unittest.TestCase.html Trial is not so well documented as the rest of Twisted, so looking at the source code has helped me a bit until I found the above tutorial. -- Martin Geisler _______________________________________________ viff-devel mailing list (http://viff.dk/) viff-devel@viff.dk http://lists.viff.dk/listinfo.cgi/viff-devel-viff.dk
