[Twisted-Python] Depreciation of trial.unittest functions?
![](https://secure.gravatar.com/avatar/7cb174aac3d9e3cbc0ebb04868f710d6.jpg?s=120&d=mm&r=g)
I'm not sure if Conch is the only project that did this, but it used the trial.unittest.* functions instead of methods on TestCases. I used them to avoid having to pass TestCase instances around all over the places, or using a global variable. To avoid the depreciation warnings, I've starting using the unittest._inst global variable, but I doubt that this is the appropriate way to change my code. Is this just not a supported way of using Trial, or is there something else I should be doing? -p -- Paul Swartz paulswartz at gmail dot com http://z3p.livejournal.com/ AIM: z3penguin GPG: 5CF0B1C9
![](https://secure.gravatar.com/avatar/1327ce755b24b956995d68accae3eab2.jpg?s=120&d=mm&r=g)
On 1/1/06, James Y Knight <foom@fuhm.net> wrote:
I'm not sure that there is a good reason for doing so. From what I can gather, the assertions in the conch tests are part of extensions to conch's application code. I think that this a Bad Thing. If Trial's assertions remain instance methods only, then the natural way of using Trial will be to put assertions in the actual test_ methods. I think that this is a Good Thing[1]. cheers, jml [1]. I think that to do otherwise is to dilute the meaning of the phrase 'unit test'.
![](https://secure.gravatar.com/avatar/1327ce755b24b956995d68accae3eab2.jpg?s=120&d=mm&r=g)
On 1/1/06, James Y Knight <foom@fuhm.net> wrote:
I'm not sure that there is a good reason for doing so. From what I can gather, the assertions in the conch tests are part of extensions to conch's application code. I think that this a Bad Thing. If Trial's assertions remain instance methods only, then the natural way of using Trial will be to put assertions in the actual test_ methods. I think that this is a Good Thing[1]. cheers, jml [1]. I think that to do otherwise is to dilute the meaning of the phrase 'unit test'.
participants (3)
-
James Y Knight
-
Jonathan Lange
-
Paul Swartz