R. David Murray <rdmur...@bitdance.com> added the comment: Meaning you want to run the same test suite with a variety of different DB connections? That seems like a reasonable use case.
Personally I find that while I sometimes create subclasses to adjust certain class parameters (thus creating a parameterized test case), more often I also have test support methods that are different between the subclasses, which would be more clumsy to do via non-subclass parameterization. Also, I do have to admit that for the case of just adjusting class constants, it would probably be a fair bit more readable to use a class parameterization scheme to express the testing variations, if only because it would pull the variations into a single cohesive block of code. So I guess I'm a +0 on this given a concrete use case. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue12600> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
